Naming Files

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

Table 80. 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 >

Oil, Gas & Electric Companies That Use Stylus Studio

Oil, gas & electric companies know a good resource when they see it. That's why they use Stylus Studio as their #1 XML resource. Come see which of these top oil, gas & electric companies are conserving their time and labor with Stylus Studio.

Saxon XSLT Processor

Stylus Studio® has partnered with Saxonica, a leading provider of Java-based XSLT and XQuery processing components to offer a robust XSLT 1.0 and 2.0 development environment, featuring development and deployment using the Saxon XSLT processor.

XML-to-XML Mapper

XML to XML mapping tools in Stylus Studio provide a powerful visual interface for mapping XML data from-and-to virtually any data format using industry-standard XSLT and XQuery technologies.

Using DTD in Java Applications

Learn how to validate XML documents using industry-standard DTD's from within your Java applications using Java DTD components including Apache Xerces and XSV.