GT 4.2.0 Migrating Guide for Java WS Core

The specification WSDL names and namespace have changed. The section WSDL Files and Namespace Changes provides a mapping from old WSDL file names and namespaces to the new equivalent. All operations in the old specification are in the new specification, so no other WSDL change should be needed.

If your service uses compact and schema directories, ensure that the new WSDLs are correctly written and deployed in schema.

The old targets for stub generation can be used as is. Ensure that modified WSDLs have been deployed to GLOBUS_LOCATION before you run the targets.

Some class and package names have changed. There is minimal change in the core infrastructure API, but the addressing package has been moved from org.apache to org.globus.

The section Package and class name changes provides a table with some mappings from old to new class names. Note this does not cover all cases, but the most commonly used code.

For changes to features and sample code, refer to the section on Code change details. The section discusses changes per feature and should provide details on how to edit your code.

Also, Constant changes provides information on some constants that have changed.

You should not have to change anything in your Ant build files or deployment infrastructure.

For samples, you can look at counter service.

The Apache WS Addressing project is being archived. So the code base has been moved to the Globus repository and has been checked into wsrf/java/lib-src/ws-addressing. The library now has org.globus package names and guarantees support only for the final version of the WS Addressing specification.

One of the key changes in the specification is that Reference Parameters are used now rather than Reference Properties. Java WS Core adds and expects EPR key information in Reference Parameters element now.

Unlike the old specification, fault cause consists of a single BaseFaultType, rather than an array of BaseFaultType. The FaultHelper utility has been modified to handle this. Now when a fault cause is added, the helper class walks through the chain of fault causes to find one without a fault cause set and then sets the new cause. Higher level services can continue to use the same API as before and faults should get serialized and deserialized correctly.

If in your testing, you look for a specific error code in a Fault Cause, it is not an array anymore. You will need to walk though the chain of fault causes. An example of such a test is testTargetedXPathQueryInvalidRP() in org.globus.wsrf.impl.properties.QueryResourcePropertiesTests.java.

The new specification allows SetTerminationTime to have either an xsd:dateTime or xsd:duration. Java WS Core currently does not support duration and only uses the xsd:dateTime value set in the request. A bug in Axis ends up with SetTerminationTime data binding having a contructor that takes two parameters.

None of the new methods in the final specification have been implemented; only a minor change in schema, which is taken care of in the providers and Simple* implementations.

Destroy was used in the old code to remove notification subscription, Unsubscribe should be used now.

 SubscriptionManager subscriptionPort =
                subscriptionManagerLocator.getSubscriptionManagerPort(
                    subscriptionEPR);

...

subscriptionPort.unsubscribe(new Unsubscribe());

This is not relevant, unless you want to write a new subcription manager and not use the one in Core.

The recent specification defines two port types for subscription manager: one with pause/resume and another without. To maintain previous functionality, the default subscription manager service provided in Core uses the pause-able subscription manager port type.

The BaseSubscriptionProvider and PausableSubscriptionProvider cover all the required functionality.

(Refer to Subscribing to Notification section above for more details on what is supported)

The interface org.globus.wsrf.Subscription has been split into two. A new interface, PausableSubcription has been introduced in the same package and contains the method for pause/resume functionality. By default, subscription support in Core uses the PausableSubcription interface only.

If pause/renew capability is required, resources need to implement PausableSubscription instead of Subscription. If you are looking to maintain old functionality, change to PausableSubscription.

All WSRF/WSN and WSA namespaces have changed. The file names have also changed, but they have been updated in the same directory. This table shows the mapping from old filenames and namespaces to the new ones.

A WS Resource specification had been added. ResourceUnknown and ResourceUnAvailableFaultType are defined in this namespace, instead of multiple definitions in lifetime and resource in the old specification.

In GT3, the business logic of the service and the state were coupled together in one class. In GT4, the business logic and the state are decoupled and placed in two separate classes. The business logic is put in a service class while the state is put in a resource class. The service is stateless while the resource is stateful. Also, GT4 introduces ResourceHome classes that are responsible for managing and discovering resources. Please see the programming model overview for details.

Even though a GT4 developer needs to modify two or three separate files the coding effort is about the same as in GT3.

In GT3, most of the configuration information was stored in the server-config.wsdd file. In GT4, since the business logic and state were decoupled, the service information is still kept in server-config.wsdd but resource information is now placed in the new jndi-config.xml file. Please see the JNDI section for more details.