I just checked in some patches into the trunk for SCOUT 18, 20, 21, 22, 25 and 26. I also updated the build a bit so it generates the uddi_v2 classes in a org.apache.ws.scout.uddi package.
I introduced one issue with this; xmlbeans starts compiling the java code and it goes off and tries to compile the entire org.apache.ws.scout package, which fails since it does not have the right classpath. However if you then run 'maven jar' from within the modules/scout directory it all works. It seems to me like a silly Maven problem, does anyone have any experience with this on how to fix the classpath? The tests now run in 'embedded' mode by default, as configured in the org.apache.ws.scout.BaseTestCase class: //LOCAL Transport final String INQUERY_URI = "org.apache.juddi.registry.local.InquiryService#inquire"; final String PUBLISH_URI ="org.apache.juddi.registry.local.PublishService#publish"; final String TRANSPORT_CLASS = "org.apache.ws.scout.transport.LocalTransport"; The only requirement is a mysql juddi database. The database is configured in modules/scout/conf/juddi.properties. It would be nice to switch this to use an embedded database. What would be a good candidate embedded database for this (Derby?) Cheers, --Kurt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
