Table of Contents
These release notes are for the incremental release 4.0.3. It includes a summary of changes since 4.0.2, bug fixes since 4.0.2 and any known problems that still exist at the time of the 4.0.3 release. This page is in addition to the top-level 4.0.3 release notes at http://www.globus.org/toolkit/releasenotes/4.0.3.
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:
- Adjusted the default size of the thread pool used by the standalone and embedded container. By default the standalone container will now have a minimum of 2 threads and a maximum of 20. The embedded container will now have a minimum of 1 thread and maximum of 3 threads.
- Refreshed version of CoG JGlobus library. Please see the CoG JGlobus Release Notes for more details.
- Updated version of Apache Commons CLI 2.0 library.
Refreshed version of Apache Axis library with the following bug fixes:
- Fault bean generation with optional primitive types
- Rare synchronization problem in symbol table
- Added more TESTS.pl scripts for interop and unit tests to integrate better with the Globus testing framework.
- Tested with Java SE 6 (Beta 2).
- Added two new usage statistics reported by Java WS Core: container uptime and a list of activated services.
The following bugs were fixed for Java WS Core:
- Bug 4204: WorkManagerImpl incorrectly implements the WorkManager.schedule(...) method
- Bug 4595: wsrf-query with a bad XPath query returns "null"
- Bug 4325: Exceptions of type 'expectedType' could be more useful
- Bug 4324: ServiceContainer reports failed startup at incorrect severity
- Bug 4540: globus-build-service.sh and Math example service error
The following problems and limitations are known to exist for Java WS Core at the time of the 4.0.3 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
- Bug 4432: SimpleTopic.notify(SOAPElement element) drop child elements
- Bug 4566: globus-deploy-gar insists that ANT_HOME be set
- Bug 5147: Unable to create javadocs on JWS Core 4.0.3
Click here for more information about this component.