GT 3.9.5 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.5 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

Parameter ordering for Axis generated files

The Java WS Core 3.9.5 contains a newer version of Axis. With that version of Axis the ordering of parameters in the constructors of generated types has changed. The parameters are now sorted alphabetically. The code that creates an instance of some generated type using a constructor with multiple arguments might need to be checked and updated appropriately. This change does not affect the code that creates an instance of some generated type using a default constructor and sets the values using the individual setter methods.

Transport security is used by default (since 3.9.4)

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 (since 3.9.4)

The Axis version distributed with Java WS Core follows the JAX-RPC specification and Java naming standards more closely then before 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

Limitations

  • WS-Notification support:
    • Only the Simple topic dialect is supported (others can be added)
    • Only flat topic spaces are supported (architecture does allow for more advanced structures)
    • Actions on the precondition, selector and policy fields in a subscription are not supported
    • When a resource is removed its subscriptions are not removed automatically
  • Only XPath resource property queries are supported (others can be added)

Known Bugs

Technology Dependencies

Java WS Core depends on the following GT components:

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

Please see the Technology Dependencies Details page for details.

Tested Platforms

Java WS Core should work on any platform that supports J2SE 1.3.1 or higher. Please note that Java WS Core will not work with GCJ.

Tested Platforms for Java WS Core

  • Linux (Red Hat 7.3)
  • Windows 2000 and XP
  • 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.