Hi, This is a patch to remove the jUDDI dependency from Scout. The related bug is: http://issues.apache.org/jira/browse/SCOUT-9
With this patch in place, Scout uses auto-generated data types from xmlbeans, and does not need jUDDI for any of it's functionality. ======= Changes ======= 1. Removed all org.apache.juddi.* dependencies. 2. Changed code to make use of xmlbeans instead. 3. Added 'xyz != null' tests in all applicable places. This particular issue became apparent when jUDDI datatype dependency was removed. For more more information, see: http://issues.apache.org/jira/browse/SCOUT-6, and http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1604 4. Moved some Registry/Transport code over from jUDDI and changed it as applicable, to remove jUDDI dependencies. 5. For the time being, a workaround of setting tmodelkey='' has been added to get around this issue in jUDDI: http://issues.apache.org/jira/browse/JUDDI-78 Without it, it would become impossible to create associations in a jUDDI registry under certain circumstances. 6. Finally, more test cases were added: JAXR01PublishOrgTest.java JAXR02QueryOrgTest.java JAXR03DeleteOrgTest.java JAXR01PublishClassificationSchemeTest.java JAXR01PublishConceptTest.java JAXR02DeleteClassificationSchemeTest.java JAXR02DeleteConceptTest.java JAXRPublishAndDeleteAssociationsTest.java JAXRPublishAndDeleteServiceBindingTest.java JAXRPublishAndDeleteServiceTest.java Some of the file names have numbers (JAXRNN*) -- these are important since some of the tests need to run in a specific order for proper coverage. It should be noted that running things should of order should NOT, cause any failures -- just that the coverage won't be optimum (e.g. if you were to run JAXR03DeleteOrgTest.java before JAXR01PublishOrgTest.java, it shouldn't fail, but delete won't be tested either, since no org has been published yet). ================ Additional Notes ================ [1] Furthermore, in an effort to make server/credential info more dynamic for the tests, the tests have a changeable inquiry/publish URL and user/password, in addition to the default configuration. The info is passed to the tests as system properties, and here they are: javax.xml.registry.queryManagerURL -- The inquiry url javax.xml.registry.lifeCycleManagerURL -- The publish url uddi.test.uid -- The user name for the uddi server (when publishing) uddi.test.pass -- The password for the above server (when publishing) [2] I am not attaching the auto-generated uddi types since it will probably reject this email due to size. Therefore, I have placed the jar here: http://people.redhat.com/dbhole/scout/jars/uddiv2-datatypes.jar The jar may also be auto-generated as follows: 1. Download the UDDI v2 specs: http://uddi.org/schema/uddi_v2.xsd 2. Run: java -classpath /path/to/xbean.jar \ org.apache.xmlbeans.impl.tool.SchemaCompiler \ -out uddiv2-datatypes.jar uddi_v2.xsd The version of xmlbeans that was used for auto-generation/testing was version xmlbeans 1.0.4. [3] In addition to running the new tests, tests were also run with JOnAS and this version of Scout -- no regressions were found in the tests. Cheers, Deepak
scout-xmlbeans.patch.bz2
Description: application/bzip
