Naming Files

File-naming conventions vary between Berkeley DB XML V1.2 and V2.0.

Table 143. Sleepycat Files Required for Stylus Studio Access
Berkeley DB XML V1.2.1	Berkeley DB XML V2.0.7 and 2.0.9
File names are not required	File names are required
File names do not have to be unique; Berkeley DB XML does, however, assign a unique ID number to each file when it is first saved to the container.	File names must be unique

Stylus Studio creates a unique pseudo-name for each named file in a container. Files without a name (supported only in Berkeley DB XML Version 1.2.1) are invisible to Stylus Studio. The pseudo-name consists of the file's name, concatenated with a pound sign (#) and the file ID assigned by Berkeley DB XML.

Example - Berkeley DB XML V 1.2.1

Consider the following files in a container as seen by Berkeley DB XML V 1.2.1:

flotsam.xml

jetsam.xml

[a file without a name]

When you display this container in the Stylus Studio Open dialog box, only these files appear:

flotsam#1.xml

flotsam#2.xml

jetsam.xml

Note that only duplicate file names are assigned a numeric ID. The fourth, unnamed, file, is not visible to Stylus Studio.

< Previous | Next >

Download a 15 Day Free Trial Now >

See What's New for 2012 in Stylus Studio X14 >

Purchase Stylus Studio X14 Now >

XML Schema Validation

Validate XML using XML Schema with MSXML, XERCES, XSV, SYSTEM.XML, & other XSD Validators. Stylus Studio's XML Schema-Aware XML Editing makes XML Schema Validation a snap!

Writing Custom XML Adapters

There are cases where the input format is too complicated for Convert to XML, or both reading and writing of the file format is needed. This section will take you through the process of writing a medium-sized adapter in Java.

EDI to XML

Using the DataDirect XML Converters EDI repository, the EDI to XML Conversion module is able to support dozens of EDI standard dialects and message types like EDIFACT, HL7, and X12.

XQuery Tools Support for TigerLogic XDMS

Stylus Studio's integration with the TigerLogic XDMS XQuery processor, allowing you to execute advanced XQuery expressions directly against any TigerLogic XDMS instance.