JAXR Home

Contents

• Read This Section First
• What This Release Includes
• Setting the Logging Level for JAXR
• Setting Properties on JAXR Connections
• Current Limitations
• Known Bugs

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_02 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:

At this release, the Java WSDP supports the Jakarta Commons Logging API. For details about changing the general default logging level, see the Java WSDP Release Notes. This section describes how to modify the logging level for JAXR.

If you use the Ant tool, you can use a <sysproperty> tag to specify a logging level for the java built-in task. For JAXR, use the following tag:

<sysproperty key="org.apache.commons.logging.simplelog.log.com.sun.xml.registry" 
      value="debug"/>

You can also use the -D option to set this property on the java command line.

You can specify any of the following logging levels:

fatal
error
warn
info
debug
trace

The default level is warn.

Logging output for JAXR appears in the terminal window.

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/protect/publishapi");
  ConnectionFactory factory = ConnectionFactory.newInstance();
  factory.setProperties(props);
  connection = factory.createConnection();
  

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

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

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

The 1.0_02 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:

• A bug in the version of the Java Secure Socket Extension (JSSE) included with the Java 2 Software Development Kit, Standard Edition (J2SE SDK), version 1.4.0, intermittently prevents publishing to the IBM and Microsoft V2 test registries. There are two workarounds for this bug:

  • On version 1.4.0 of the J2SE SDK, specify the option -DuseSOAP=true to the java command when you run a JAXR client program. If you use the Ant tool, you can also use the following <sysproperty> tag in your build.xml file:

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

  • Use version 1.4.0_01 of the J2SE SDK (available from http://java.sun.com/j2se/1.4/index.html) instead of version 1.4.0. This version includes a fixed version of the JSSE library.

• 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.