[juddi-Users] FYI Major jUDDI source changes...

[Steve Viens <st...@inflexionpoint.com>]

I've made and committed to CVS lots of changes this morning - vertually
every class was altered in some way (mostly minor changes though) and
I've also updated the uddi4j jar to correct a couple of bugs that the
UDDI4j team is working to fix right now.

I'd be very happy to help you make jUDDI work for you and I should be
online for most of the day and weekend and I will respond as quickly as
possible to any problems you may be having. Any feedback would be
greatly appreciated. I'm planning to make an announcement of the jUDDI
Beta release to the jUDDI-Users and jUDDI-Announce mailing lists as well
as posting something to the SourceForge Java Foundry and FreshMeat.com.

The UDDI4j fix corrects a problem when a UDDI error is reported back to
the calling client/proxy. Also, the most significant of the changes (and
will require you to make a config change).

If you're using the local HSQL database then you should be using
"HSQLDataStoreFactory" - if you wish to use a different DBMS then you
should be using "JDBCDataStoreFactory". 

The JDBCDataStoreFactory now requires the web app container (Tomcat,
WebSphere, etc) to have a JDBC DataSource defined and named
'jdbc/juddidb' - instructions for how to set this up on Tomcat will be
included in the jUDDI Users Guide shortly ... The HSQLDataStoreFactory
has no such requirement and is the default DataStoreFactory (this simply
uses a local HSQLdb database).

I apologize for any inconvenience. From this point forward any/all
changes will be handled and reported to the appropriate jUDDI lists in a
more controlled and professional manner.

Steve

Steve Viens
jUDDI Project Manager
sviens@users.sourceforge.net
http://www.juddi.org