Changes between Version 28 and Version 29 of ebXMLObjectModel

Timestamp:

Jul 30, 2008, 2:53:03 PM (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 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]. For each of these objects there is a testcase for marshalling and a testcase for unmarshalling. As we're dealing with XML the tests use the complimentary test library [http://xmlunit.sourceforge.net/ XML Unit]. This allows a.o. to ignore differences in whitespace and the ordering of elements and attributes in the XML where that should be ignored. The test suite will be incorporated into the Continuous Integration build process.
+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]. For each of these objects there is a testcase for marshalling and a testcase for unmarshalling. As we're dealing with XML the tests use the complimentary test library [http://xmlunit.sourceforge.net/ XML Unit]. This allows a.o. to ignore differences in whitespace and the ordering of elements and attributes in the XML where that should be ignored. An automatic run of the test suite has been incorporated into the Ant build script and will be made part of the Continuous Integration build process.
 
 
@@ -77 +77 @@
  }}}
 
-A perhaps remarkable feature of JiBX is that it requires a post-compilation step where the [http://jibx.sourceforge.net/bindcomp.html JiBX binding compiler] generates the binding code. Although it can be skipped and the binding done at runtime, doing this improves performance and also helps signaling possible errors in the binding definition. This will be made part of the automated build process.
+A perhaps remarkable feature of JiBX is that it requires a post-compilation step where the [http://jibx.sourceforge.net/bindcomp.html JiBX binding compiler] generates the binding code. Although it can be skipped and the binding done at runtime, doing this improves performance and also helps signaling possible errors in the binding definition. This has been made part of the automated build process.
 
 For the developers amongst you, there is an [http://jibx.sourceforge.net/eclipse/index.html Eclipse plugin] available that will automatically run the binding compiler every time you build.