Java WSDP Registry Server Home

Java^TM Web Services Developer Pack (Java WSDP)
Registry Server 1.0_06 Release Notes

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
• Using the Registry Server with the Security Manager
• Current Limitations
• Known Bugs

Read This Section First

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

The service end point for the Java WSDP Registry Server is http://localhost:8080/RegistryServer. The service end point can be changed by editing the property values in <JWSDP_HOME>/jwsdp-shared/bin/launcher.xml:
<sysproperty key="org.apache.xindice.host" value="desired Xindice host"/>
<sysproperty key="org.apache.xindice.port" value="desired Xindice port"/>

Note: The file <JWSDP_HOME>/registry-server/webapps/RegistryServer.war may only be used for the purposes of designing, developing, and testing programs.

What This Release Includes

This release includes

• The Java WSDP Registry Server 1.0_06 release
• The Xindice database, the repository for registry data

You can also use the Registry Browser and sample programs provided by the Java API for XML Registries (JAXR) to create and query registry data. When you use JAXR or any other UDDI capable application with the Java WSDP Registry Server, the service end point is http://localhost:8080/RegistryServer

This release implements Version 2 of the Universal Description, Discovery and Integration (UDDI) project, including

• UDDI Version 2.00 API Specification Errata 3
• UDDI Version 2.00 Data Structure Reference Errata 2

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

Using the Registry Server with the Security Manager

To use the Registry Server with the security manager turned on, add these permissions to the file <JWSDP_HOME>/conf/catalina.policy:

grant codeBase "file:${catalina.home}/work/Standard Engine/localhost/RegistryServer/WEB-INF/classes/-" {
   permission java.io.FilePermission "${catalina.home}/jaxp/lib/endorsed/xercesImpl.jar", "read";
   permission java.io.FilePermission "${catalina.home}/jaxp/lib/endorsed/xalan.jar", "read";
   permission java.io.FilePermission "${catalina.home}/bin/orb.properties", "read";
   permission java.util.PropertyPermission "*", "read, write";
   permission java.net.SocketPermission "*", "listen,connect,resolve";
};

Current Limitations

The 1.0_06 release of the Java WSDP Registry Server has the following limitations:

• The find_relatedBusinesses message is not supported.
• For <find_*> messages, the find qualifiers orLikeKeys, combineCategoryBags, and serviceSubset are not supported. All other find qualifiers are supported.

Known Issues

At this release, the Java WSDP Registry Server has the following known issues:

• Because the find_relatedBusinesses request message is not supported in this release (see Current Limitations), use of the JAXR API findAssociations method will fail with the Registry Server. The Registry Server will return an E_unsupported message in a SOAP Fault if find_relatedBusinesses is used.
• The jwsdponsunone integration script does not support the deployment of the Registry Server on Sun ONE Application Server 7 (S1AS7). The reason is that S1AS7 has a dependency on the Crimson parser, while the Registry Server depends on the Xerces parser. It is not possible to use Xerces for only the Registry Server web application without affecting the server; therefore, we do not support this combination.

  The workaround is to use Registry Server with the Java WSDP for applications deployed on S1AS7. You may start the Java WSDP Tomcat and run it at the same time as S1AS7 with no conflict.

• The Java WSDP Registry Server depends on the version of the Xerces parser that is part of the Java WSDP. If you do a custom installation and use a version of Tomcat other than the Java WSDP version, make sure that you either set the java.endorsed.dirs system property to <JWSDP_HOME>jaxp/lib/endorsed or copy the files in the <JWSDP_HOME>jaxp/lib/endorsed directory to <JAVA_HOME>/jre/lib/endorsed, as instructed in the Java WSDP Release Notes.