jUDDI 0.8.0 Release Notes

This is the 0.8.0 release of the jUDDI Web Services Discovery Toolkit.

About this release

This release... TO-DO

Changes From 0.7.2 to 0.8.0


  1. The version of Axis included with jUDDI is now
     Axis 1.1 Final. The 'log4j.properties' file
     that is bundled within axis.jar has been removed
     to avoid conflicts with the log4j.properties
     file in jUDDI's WEB-INF/classes directory.

  2. Log4j is now accessed through Jakarta's
     commons-logging package.

  3. <env-entry> values for juddi.propsFile
     and log4j.propsFile are no longer requred.
     Instead the juddi.properties and
     log4j.properties files are looked up in
     the classpath.

     This means that for the jUDDI webapp these
     files should be located in the WEB-INF/lib
     directory (they are copied from juddi/conf
     into this directory the build process).

  4. A jUDDI client has been added bringing
     jUDDI full-circle back to being a UDDI
     toolkit (beginnings of one). Take a look
     at org.juddi.registry.RegistryProxy and
     also take a look at the contents of the
     juddi/samples directory.

  5. The beginnings of an admin API has been
     introduced with the addition of four
     jUDDI-proprietary API calls (which are
     still under construction).

         save_publisher
         get_publisherDetail
         delete_publisher
         find_publisher

     This introduced several new classes:

       org.juddi.datatype.request.SavePublisher
       org.juddi.datatype.request.GetPublisherDetail
       org.juddi.datatype.request.DeletePublisher
       org.juddi.datatype.request.FindPublisher
       org.juddi.datatype.publisher.PublisherID
       org.juddi.datatype.response.PublisherList
       org.juddi.datatype.response.PublisherDetail
       org.juddi.datatype.response.PublisherInfo
       org.juddi.datatype.response.PublisherInfos

	Handlers for each of the classes above have
	also been created in the org.juddi.handlers
	package.


  6. Added support for the 'generic' attribute
     to the UDDI Response messages (this was
     being handled in the AxixRequestHandler).
     Also updated all associated Handler
     classes to marshal/unmarshal this value.

  7. The org.juddi.registry.functions package
     was moved/renamted to org.juddi.functions.

  8. (bug-fix) Added a default constructor to
     org.juddi.datatype.response.PublisherAssertions

  9. (bug-fix) Added support for mashalling &
     unmarshalling the 'operator' value to
     org.juddi.handler.PublisherAssertionsHandler.

 10. Expanded the PUBLISHER table to support the
     new jUDDI Admin API

     *** THIS IS IMPORTANT TO NOTE AS ANY EXISTING
     jUDDI IMPLEMENTATION WILL NEED TO MAKE THIS
     CHANGE BEFORE USING THE MOST MOST RECENT JUDDI
     SOURCE!!!

     The 0.7.0 and 0.7.1 PUBLISHER table:

	  CREATE TABLE PUBLISHER
	  (
	    PUBLISHER_ID VARCHAR(20) NOT NULL,
	    PUBLISHER_NAME VARCHAR(255) NOT NULL,
	    ADMIN VARCHAR(5) NULL,
	    PRIMARY KEY (PUBLISHER_ID)
	  );

     The new PUBLISHER table:
     (from ddl/juddi_mysql.ddl)

	  CREATE TABLE PUBLISHER
	  (
	    PUBLISHER_ID VARCHAR(20) NOT NULL,
	    PUBLISHER_NAME VARCHAR(255) NOT NULL,
	    LAST_NAME VARCHAR(150) NULL,
	    FIRST_NAME VARCHAR(100) NULL,
	    MIDDLE_INIT VARCHAR(5) NULL,
	    WORK_PHONE VARCHAR(50) NULL,
	    MOBILE_PHONE VARCHAR(50) NULL,
	    PAGER VARCHAR(50) NULL,
	    EMAIL_ADDRESS VARCHAR(255) NULL,
	    ADMIN VARCHAR(5) NULL,
	    ENABLED VARCHAR(5) NULL,
	    PRIMARY KEY (PUBLISHER_ID)
	  );

 11. The following two methods have been removed
     from the abstract 'Handler' class and all
     subclasses (lots of them) and any imports
     that were required by these methods.

      RegistryObject unmarshal(SOAPElement e)
      void marshal(RegistryObject o,SOAPElement e)

     These were never completely implemented
     or used by jUDDI.

 12. Added new 'test' and 'checkstyle' Ant
     tasks.

 13. The happyjuddi.jsp page has been updated
     with several great new 'debugging' features.

 14. When specifying a JNDI name for a JDBC
     DataSource in jUDDI's juddi.properties file
     you must now use a fully qualified name.

      Old way (0.7.2 and earlier):

        juddi.dataSource=jdbc/juddiDB

      New way: (0.8.0 and later):

        juddi.dataSource=java:comp/env/jdbc/juddiDB

 15. Both getGeneric() and setGeneric() methods were
     added to the following list of classes in the
     org.juddi.datatype.response package: 

	  AssertionStatusReport
	  AuthToken
	  BindingDetail
	  BusinessDetail
	  BusinessDetailExt
	  BusinessList
	  PublisherAssertions
	  RegisteredInfo
	  RelatedBusinessList
	  ServiceDetail
	  ServiceList
	  TModelDetail
	  TModelList
	
	 The following handler classes from the 
	 the org.juddi.handler package were updated
	 to marshal/unmarshal the new generic value.
	
	  AssertionStatusReportHandler
	  AuthTokenHandler
	  BindingDetailHandler
	  BusinessDetailHandler
	  BusinessDetailExtHandler
	  BusinessListHandler
	  PublisherAssertionsHandler
	  RegisteredInfoHandler
	  RelatedBusinessListHandler
	  ServiceDetailHandler
	  ServiceListHandler
	  TModelDetailHandler
	  TModelListHandler

   This value was being set in the AxisProcessor 
   (in org.juddi.transport.axis). All associated
   unit test methods within the XxxxHandler classes
   were updated as well.

Changes From 0.7.1 to 0.7.2

  TO-DO

Changes From 0.7.0 to 0.7.1

  TO-DO

Changes From 0.6.2 to 0.7.0

  TO-DO

Changes From 0.6.1 to 0.6.2

  TO-DO

Changes From 0.6.0 to 0.6.1

  TO-DO

Changes From 0.5.1 to 0.6.0

  TO-DO

More Info

Please check out the included documentation and the FAQ for more information.

How You Can Help

Coding, testing, and helping to answer questions on the juddi-users list are all greatly appreciated. We particularly encourage you to submit improvements to the documentation, however large or small and in any format, to juddi-developers@lists.sourceforge.net.

Thanks for your interest in jUDDI!

-- The jUDDI Development Team