GT 3.9.3 Development Release Notes for Java WS Core
- Component Overview
- Feature Summary
- Bug Fixes
- Known Problems
- Technology Dependencies
- Tested Platforms
- Backward Compatibility Summary
- For More Information
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.3 release
- Implementation of the OASIS WSRF and WSN working drafts specifications (with minor fixes to the 1.2-draft-01 published schemas and with March 2004 version of WS-Addressing specification)
- 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 support
- Subscription persistence and recovery
- Automatic service and ResourceHome activation on startup
- Operation providers
- Support for both Windows and Unix systems
Deprecated Features
- None.
Bug Fixes
Known Problems
- Bug 1172
- In rare occasions, notification consumer might not receive all the notifications it is expecting.
-
On certain platforms and that support
/dev/randomdevice, firing lots of notifications might cause the system to ran out of entropy. And that might cause significant delays in delivering notifications, too many threads created at the same time and/or OutOfMemoryError.
Technology Dependencies
Java WS Core depends on the following GT components:
Java WS Core depends on the following 3rd party software:
- Apache Xerces 2.6.2
- Apache XML Security 1.0.4
- Apache Axis 1.2
- Apache Xalan 2.6.0
- Apache Addressing
- Apache Commons BeanUtils
- Apache Commons CLI
- Apache Commons Collections
- Apache Commons Digester
- Concurrent Library
- Apache Tomcat JNDI
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
ServiceDatais replaced byResourcePropertyandServiceDataSetis replaced byResourcePropertySet.
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 March 2004 version of WS-Addressing specification.)
For More Information
Please see Java WS Core documentation for more information.