Changes between Version 5 and Version 6 of ebXMLObjectModel

Timestamp:

Jul 21, 2008, 8:21:34 AM (16 years ago)

Author:

heikki

Comment:

--

ebXMLObjectModel

@@ -35 +35 @@
 Note: the Access Control section of the Information Model specification is not (yet) part of the implementation.
 
-The implementation is complemented with a set of unit tests, for each of the objects that may be used as a top-level element in an ebXML document. The unit tests are written in the well-known [http://www.junit.org/ Junit framework]. The testcases are for each of these objects, a test for marshalling, and a test for unmarshalling. As we're dealing with XML the tests use the complimentary test library [http://xmlunit.sourceforge.net/ XML Unit]. This allows o.a. to ignore differences in whitespace and the order of elements in the XML where that should be ignored.
-
-
+The implementation is complemented with a suite of unit tests, for each of the objects that may be used as a top-level element in an ebXML document. The unit tests are written in the well-known [http://www.junit.org/ Junit framework]. The testcases are for each of these objects, a test for marshalling, and a test for unmarshalling. As we're dealing with XML the tests use the complimentary test library [http://xmlunit.sourceforge.net/ XML Unit]. This allows o.a. to ignore differences in whitespace and the order of elements in the XML where that should be ignored. The test suite will be incorporated into the Continuous Integration build process.
 
 
@@ -44 +42 @@
 === XML binding ===
 
+In order to efficiently create an XML binding, that is to say the ability to marshal and unmarshal XML documents, the Java Beans implementation is decorated with a [http://jibx.sourceforge.net/ JiXB binding]. JiXB was chosen over other binding frameworks such as [http://xmlbeans.apache.org/ XMLBeans], [http://www.castor.org/ Castor] and [https://jaxb.dev.java.net/ JAXB] because of its [high performance high performance], ease of use, and non-intrusive programming model.
+
+An sample of code that marshals a !RegistryObject document is the following. This and similar code you can find in the Object Model's unit test suite.
+
+ {{{
+
+    IBindingFactory bfact = BindingDirectory.getFactory(RegistryObject.class);
+    IMarshallingContext marshallingContext = bfact.createMarshallingContext();
+    Writer out = new BufferedWriter(new OutputStreamWriter(new ByteArrayOutputStream()));
+    marshallingContext.setOutput(out);
+    // pretty-print the XML output
+    marshallingContext.setIndent(3);
+    marshallingContext.marshalDocument(o, "UTF-8", null);
+
+
+ }}}
+
+
+
+
 ----