Table of Contents
These release notes are for the incremental release 4.0.2. It includes a summary of changes since 4.0.1, bug fixes since 4.0.1 and any known problems that still exist at the time of the 4.0.2 release. This page is in addition to the top-level 4.0.2 release notes at http://www.globus.org/toolkit/releasenotes/4.0.2.
For release notes about 4.0 (including feature summary, technology dependencies, etc) go to the Java WS Core 4.0 Release Notes.
The following changes have occurred for Java WS Core:
- Added Tomcat 5.5.x support.
- Added TEST.pl for unit tests to integrate with Globus testing framework.
- Fixed additional cases where WS-Addressing headers were not added to the SOAP Fault messages.
The following bugs were fixed for Java WS Core:
- Bug 3651: Misspelled Deserialization in exception message
- Bug 3737: Support for socket timeouts on the server side
- Bug 3750: Allow for setting the location where the persistence files are stored
- Bug 3259: Generated Unix scripts cannot handle certain variables with spaces
- Bug 3776: globus-start-container requires user to delete orphaned pid file
- Bug 3899: globus-stop-container-detached does not give the container the chance to finish normally
- Bug 3813: Race condition in container creation/shutdown
- Bug 3814: Problem shutting down the container from within one of its threads
- Bug 3863: ResourcePropertyTopic sendOldValue is ignored
- Bug 3932: Problems with white space when passing options to Windows versions of command wrappers
- Bug 3889: Newline missing when using core serialization utility
- Bug 4107: Notification deadlock
- Bug 4188: Container fails on expired proxy and cannot recover
- Bug 4325: Exceptions of type "expectedType" could be more useful
The following problems and limitations are known to exist for Java WS Core at the time of the 4.0.2 release:
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)
- A resource might not get destroyed at the exact time as indicated by the scheduled termination time. A sweeper thread that removes expired resources runs periodically (every 1 minute by default) so an expired resource might not get removed until the next time the sweeper thread runs.
- SOAP messages with attachments are not supported. In fact, the Axis version distributed with GT was compiled without attachment support.
- In certain cases, the "
dialect" attribute of TopicExpression or QueryExpression is not serialized properly as defined in the schema. An "org.globus.dialect.attr.qualified" Java system property was added to control how the serialization of thedialectattribute. Please see the Bug 3513 for details.
Known Bugs
- Bug 2471: Message security signature verification issues
- Bug 2445: Same input and output messages in WSDL confuse Axis
- Bug 2921: Support for TerminationTimeChangeRejectedFault
- Bug 2926: Local transport does not work without a current MessageContext
- Bug 3113: Processing by the WSDLPreprocessor produces output different depending on the JVM
- Bug 3482: wsa:From is not set correctly when service calls another service
- Bug 3483: xsd:anyType not serialized correctly
Click here for more information about this component.