JAXR Home

For an updated, online version of these release notes, see Release Notes.

Revised: 09/26/2003

Contents

• Read This Section First
• What This Release Includes
• Setting Properties on JAXR Connections
• Current Limitations
• Known Issues

Before you work with this release, make sure that you have installed the required software and are on a supported operating system. You can find this information in the Java^TM Web Services Developer Pack (Java WSDP) home page and Release Notes and the JAXR home page.

This release includes

• The JAXR 1.0.5 Reference Implementation (RI)
• API documentation
• Sample programs, including a Registry Browser

This release implements version 1.0 of the JAXR specification. The specification is available from the JAXR downloads page, http://java.sun.com/xml/downloads/jaxr.html.

The JAXR RI release contents are arranged in the following structure within the Java WSDP release:

The implementation of JAXR in the Java WSDP allows you to set a number of properties on a JAXR connection. Some of these are standard properties described in the JAXR specification. Others are implementation-specific properties. The following tables list and describe these properties.

     id1,id2|id3,id4

You can set these properties as follows:

• Most of these properties must be set in a JAXR client program. For example:

  Properties props = new Properties();
  props.setProperty("javax.xml.registry.queryManagerURL",
      "http://uddi.ibm.com/testregistry/inquiryapi");
  props.setProperty("javax.xml.registry.lifeCycleManagerURL", 
      "https://uddi.ibm.com/testregistry/publishapi");
  ConnectionFactory factory = ConnectionFactory.newInstance();
  factory.setProperties(props);
  connection = factory.createConnection();
  

• The postalAddressScheme and useCache properties may be set in a <sysproperty> tag in a build.xml file for the Ant tool. For example:

  <sysproperty key="useCache" value="true"/>
  

  These properties may also be set with the -D option on the java command line.

The 1.0.5 release of the JAXR RI has the following limitations:

• It implements the level 0 capability profile of the JAXR specification, not the level 1 capability profile. It is compatible with Version 2 of the Universal Description, Discovery and Integration (UDDI) specification.
• It supports access to UDDI registries but not to ebXML registries. More specifically, it supports access to Version 2 UDDI registries but not to Version 1 UDDI registries.
• It does not implement the optional DeclarativeQueryManager interface.
• It does not provide a preconfigured connection factory that can be placed in a Java Naming and Directory Interface^TM (JNDI) API namespace.

At this release, the JAXR RI has the following known issues:

• If you publish an organization to the IBM or Microsoft V2 test registry on the Linux or Microsoft Windows platform, it ignores any Description value that you specify for a User. This problem does not occur on the Solaris platform.
• Because the Java WSDP Registry Server does not support the find_relatedBusinesses request message at this release, use of the JAXR API findAssociations method will fail with the Registry Server. For details, see the Java WSDP Registry Server Release Notes.
• If you start the JAXR Registry Browser and immediately choose the publish URL for the Microsoft registry, you may see error messages like the following:

  [ERROR] registry - -java.lang.ClassNotFoundException: 
  com/sun/xml/registry/uddi/bindingsv2/Soap:Fault
  java.lang.ClassCastException
      at 
  com.sun.xml.registry.common.util.CastorUtil.unmarshalObject(Unknown Source)
      at com.sun.xml.registry.uddi.Processor.processResponse(Unknown Source)
      ....
  

  You may safely ignore these messages. To avoid them, choose a query URL first after you start the Registry Browser.