Table of Contents
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 APIs and tools for building stateful Web services. The Java WS Core provides a Java-based container (web services hosting environment) and is the default container in a default GT installation. Commands can be used with any WSRF-based service/resource. The following GT 4.2.1 components are based on the Java WS Core [fixme verify]:
New Features in the GT 4.2 release
- Persistent HTTP/S connection support (client and server side)
- Support for SOAP with Attachments (DIME, MIME, and MTOM formats). See the SOAP Attachments section for details.
- Dynamic deployment support for the standalone container. See the Java WS Core Container Dynamic Deploy Design Document for more information.
- WS-Enumeration support. See the Java WS Core WS-Enumeration Design Document for more information.
- JBOSS 4.0.x support.
- The TargetedXPath query dialect implementation that enables simpler and more efficient querying of resource property documents.
Other Supported Features
- A standalone and embeddable container
- Tomcat 4.1, 5.0, and 5.5 support
- Basic API for resource persistence and recovery
- Persistent subscriptions support
- Automatic service and ResourceHome activation on startup
- Operation providers
Deprecated Features
- None
- Bug 6106: Security descriptor validation on deploy target fails with valid descriptors
- Bug 6268: cannot make the "ServiceInvocation " example work becese of authentication error:
- Bug 6296: Endorsed directory not set up correctly
- Bug 6395: Authorization directory default value in source distributions incorrect
- Bug 6083: Add EPR to logging information
- Bug 6264: NullPointerException in org.globus.wsrf.encoding.FaultCauseSerializer
- Bug 6315: Security tests fail with parsing of invalid descriptor
- Bug 6340: Problems with Test on Java WS Core
- Bug 6257: Not found org.globus.wsrf.core.query package
The following problems and limitations are known to exist for Java WS Core at the time of the 4.2.1 release:
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.
Java WS Core depends on the following GT components:
Java WS Core depends on the following 3rd party software:
Please see Java WS Core Technical Dependencies Details for details.
Java WS Core should work on any platform that supports J2SE 1.4.1 or higher.
Tested platforms for Java WS Core:
- Linux (Debian 3.1)
- Windows XP
- Solaris 9
Tested JVMs for Java WS Core:
- Sun JVM 1.4.2, 1.5.0, and 1.6.0 RC
- IBM JVM 1.4.1, and 1.4.2
- BEA JRockit JVM 1.5.0
JVM notes:
Tested containers for Java WS Core:
- Java WS Core container
- Tomcat 4.1.34
- Tomcat 5.0.30
- Tomcat 5.5.20
- JBoss 4.0.2
Protocol changes since GT version4.2.0:
For a migration guide for GT 4.0.x services, please see this document.
API changes since GT version4.2.0:
- None
Schema changes since GT version4.2.0:
- None
Other changes since GT version4.2.0:
- None
Associated standards for Java WS Core:
Please see Java WS Core for more information.
R
- ResourceHome
In Java WS Core, resources are managed and discovered via ResourceHome implementations. The ResourceHome implementations can also be responsible for creating new resources, performing operations on a set of resources at a time, etc. ResourceHomes are configured in JNDI and are associated with a particular web service.
W
- Web Services Notification (WSN)
The WS-Notification family of specifications define a pattern-based approach to allowing Web services to disseminate information to one another. This framework comprises mechanisms for basic notification (WS-Notification), topic-based notification (WS-Topics), and brokered notification (WS-BrokeredNotification). See the OASIS Web Services Notification (WSN) TC for details.
- Web Services Resource Framework (WSRF)
Web Services Resource Framework (WSRF) is a specification that extends web services for grid applications by giving them the ability to retain state information while at the same time retaining statelessness (using resources). The combination of a web service and a resource is referred to as a WS-Resource. WSRF is a collection of different specifications that manage WS-Resources.
This framework comprises mechanisms to describe views on the state (WS-ResourceProperties), to support management of the state through properties associated with the Web service (WS-ResourceLifetime), to describe how these mechanisms are extensible to groups of Web services (WS-ServiceGroup), and to deal with faults (WS-BaseFaults).
For more information, go to: http://www.globus.org/wsrf/ and OASIS Web Services Notification (WSRF) TC .