The registry implementation has two separate and distinct uses for accessing XML documents from Java using bindings created by JAXB:
The JAXB page on java.sun.com currently (June 2004) defines JAXB as:
Java Architecture for XML Binding (JAXB) provides a convenient way to bind an XML schema to a representation in Java code. This makes it easy for you to incorporate XML data and processing functions in applications based on Java technology without having to know much about XML itself.
There is an introductory article on JAXB at http://java.sun.com/developer/technicalArticles/WebServices/jaxb/.
Creating the binding code is part of the ebxmlrr-spec project, not the omar project, since:
The jar files for the binding source code, compiled class files, and documentation are included in the omar distribution.
You need the ebxmlrr-spec project to be able to generate the binding.
There are three Ant targets in the ebxmlrr-spec project that are useful:
oasis-regrep.jar and oasis-regrep-doc.jar are in misc/lib (as is oasis-regrep-src.jar which contains the source code), and all three are copied into build/lib when you build nearly any target.
To give an idea how often the binding is used, at the time of this writing, the binding classes are used by classes in the following packages:
The jar files for the bindingcompiled binding and its documentation only are included in the omar distribution.
The schema for the user interface configuration XML files is at src/java/org/freebxml/omar/client/ui/common/conf/browserConfig.xsd.
There are two Ant targets in the omar project that are useful:
It is not surprising that, at the time of this writing, the binding classes are used only within client packages: