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

2. Tested platforms

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:

GCJ is not supported.
If using IBM JVM 1.4.1 please see bug 2828 for more information.

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

3. Backward compatibility summary

Protocol changes since GT version4.0.x:

Upgrade to WS-Addressing 1.0
Upgrade to WSRF 1.2
For an overview of the changes and links to the new specifications, please see this document.
For a migration guide for GT 4.0.x services, please see this document.

API changes since GT version4.0.x:

Java WS Core now requires Java 1.5 to compile and run. Java 5 provides new concurrency capabilities as well as Annotations and Generics (as well as some other features). For details on the new features, please see this overview. While it is possible that Java WS Core could run under Retroweaver or Retrotranslator, this has not been tested. Java 5 is available for most platforms from Sun http://java.sun.com/javase/downloads/index_jdk5.jsp
The faultCause field in the BaseFaultType class is no longer an Object. Instead it has been changed to a BaseFaultTypeFaultCause. This class, in turn, contains an object that represents the actual fault cause called causeElement. This change was made in order to support interoperability with other groups.

Schema changes since GT version4.0.x:

Please see the Protocol Changes section

Other changes since GT version4.0.x:

Java 1.5 is required to use Java WS Core 4.2.

4. Technology dependencies

Java WS Core depends on the following GT components:

Java CoG Kit

Java WS Core depends on the following 3rd party software:

Please see Java WS Core Technical Dependencies Details for details.

5. Security Considerations for Java WS Core

5.1. Permissions of service configuration files

The service configuration files such as jndi-config.xml or server-config.wsdd (located under $GLOBUS_LOCATION/etc/<gar>/ directory) may contain private information such as database passwords, etc. Ensure that these configuration files are only readable by the user that is running the container. The deployment process automatically sets the permissions of the jndi-config.xml and server-config.wsdd files as user readable only. However, this might not work correctly on all platforms and this does not apply to any other configuration files.

5.2. Permissions of persistent data

The services using subscription persistence API or other basic persistence helper API will store all or part of its persistent data under the ~/.globus/persisted directory. Ensure that the entire ~/.globus/persisted directory is only readable by the user running the container.

5.3. Invocation of non-public service functions

A client can potentially invoke a service function that is not formally defined in the WSDL but it is defined in the service implementation class. There are two ways to prevent this from happening:

Define all service methods in your service class as either private or protected.
Configure appropriate allowedMethods or allowedMethodsClass parameter in the service deployment descriptor (please see Configuring Java WS Core for details).

Prev		Next
Java WS Core : Developer's Guide	Home	Programming Recipes