GT 3.9.4 Development Release Notes for Java WS Core

Component Overview

The Java WS Core is an implementation of the Web Services Resource Framework (WSRF) and the Web Service Notification (WSN) family of standards. It provides API and tools for building stateful Web services.

Feature Summary

New Features in the GT 3.9.4 release

  • Implementation of the OASIS WSRF and WSN working drafts specifications (with minor fixes to the 1.2-draft-01 published schemas and with the March 2004 version of the WS-Addressing specification)
  • Basic HTTP/1.1 client & server support
  • JNDI based registry based on the JNDI service in Apache Tomcat
  • An implementation of the Work Manager and Timer specifications

Other Supported Features

  • A standalone and embeddable container
  • Tomcat 4.1 and 5.0 support
  • Basic API for resource persistence and recovery
  • Persistent subscriptions support
  • Automatic service and ResourceHome activation on startup
  • Operation providers

Deprecated Features

  • None

Changes Summary

Transport security is used by default

The transport security (HTTPS) is now assumed as a default security mechanism. For example, the standalone container will now start in a transport secure mode (HTTPS container running on port 8443). The plain (HTTP) container can still be started with -nosec option. Please see globus-start-container documentation for details.

Different naming scheme for Axis generated files

The Java WS Core 3.9.4 contains a newer version of Axis. This Axis version follows the JAX-RPC specification and Java naming standards more closely when naming the generated files (generated by wsdl2java process). The code generated is exactly the same as before but the names of the files are slightly different. The changes to the names are pretty straightforward: All underscores are dropped, the first letter of each word within the name is capitalized. If there are collisions between names (for example, the port type name is the same as some element name), the name for the port type will end with _PortType and for the element with _Element. Examples: 

foo.java -> Foo.java
_Foo_Bar.java -> FooBar.java

_GetMultipleResourceProperties.java -> GetMultipleResourceProperties_Element.java
GetMultipleResourceProperties.java -> GetMultipleResourceProperties_PortType.java

Bug Fixes

Known Problems

  • Bug 2358
  • Bug 2177
  • In rare occasions, notification consumer might not receive all the notifications it is expecting.

Technology Dependencies

Java WS Core depends on the following GT components:

Java WS Core depends on the following 3rd party software:

Tested Platforms

Java WS Core should work on any platform that supports J2SE 1.3.1 or higher.

Tested Platforms for Java WS Core

  • Linux (Red Hat 7.3)
  • Windows 2000
  • Solaris 9

Backward Compatibility Summary

Protocol changes since GT version 3.2

  • HTTP/1.1 with 'chunked' transfer encoding is now used by default.
  • Wire messages follow the new schemas and therefore are completely different (see below.)

API changes since GT version 3.2

  • Majority of the API are new. Some API resembles GT 3.2 API, for example ServiceData is replaced by ResourceProperty and ServiceDataSet is replaced by ResourcePropertySet.

Schema changes since GT version 3.2

  • Schemas are completely new. The WS Java Core implements the OASIS WSRF and WSN working drafts specifications (with minor fixes to the 1.2-draft-01 published schemas and with the March 2004 version of the WS-Addressing specification.)

For More Information

Please see Java WS Core documentation for more information.