Web Services: What's new in this release
This release adds support for new specifications such as: JAX-WS, JAXB, SOAP 1.2, MTOM, policy sets, WS-Addressing, and WS-RM. This enables interoperable reliable, asynchronous Web services and support for the Java™ API for XML Web Services (JAX-WS) 2.1 programming model. You must have selected to install the WebSphere® Application Server v6.1 Feature Pack for Web Services server and tooling or WAS v7.0 in order to exploit these new standards.
Several new Web services standards are supported by this development environment. These include:
- Java API for XML Web Services (JAX-WS) 2.1 - JSR-224
- Java API for XML Web Services (JAX-WS) is a new programming model that simplifies application development through support of a standard, annotation-based model to develop Web services applications and clients. The JAX-WS 2.1 programming standard aligns itself with the document-centric messaging model and replaces the remote procedure call programming model defined by the Java API for XML-based RPC (JAX-RPC) specification.
- Java Architecture for XML Binding (JAXB) 2.1 - JSR-222
- Java Architecture for XML Binding (JAXB) is a Java technology that provides an easy and convenient way to map Java classes and XML schema for simplified development of Web services. JAXB leverages the flexibility of platform-neutral XML data in Java applications to bind XML schema to Java applications without requiring extensive knowledge of XML programming.
- Web Services Metadata 2.0 (JSR-181) and A Metadata Facility for the Java Programming Language (JSR-175)
- Both JAX-WS and JSR-181 introduce a JSR-175 style annotations programming model which aims to make it easier for users to create and modify a Web Service. The annotations embed metadata in the compiled .class file of Web Service implementations and service endpoint interfaces which can be processed at runtime much like deployment descriptors.
- SOAP 1.2
- SOAP 1.2 provides a more specific definition of the SOAP processing model, which removes many of the ambiguities that sometimes led to interoperability problems in the absence of the Web Services-Interoperability (WS-I) profiles.
- SOAP Message Transmission Optimization Mechanism (MTOM)
- SOAP MTOM provides vendor interoperable attachment support for sending binary attachments, including images or files, with your Web services request.
- Policy Sets
- Policy sets are used to simplify your Web service Quality of Service (QOS) configuration. Policy sets combine configuration settings, including those for transport and message level configuration, such as WS-Addressing, WS-ReliableMessaging, WS-SecureConversation, and WS-Security.
- WS-Security 1.1 enhancements
- The WS-Security 1.1 standard brings several new enhancements to the security component, including Web Services Secure Conversation (WS-SecureConversation).
- Web Services Addressing (WS-Addressing) enhancements
- Web Services Addressing (WS-Addressing) is a Worldwide Web Consortium (W3C) specification that aids interoperability between Web services by defining a standard way to address Web services and provide addressing information in messages. The WS-Addressing specification introduces two primary concepts: endpoint references and message addressing properties.
- Web Services Reliable Messaging (WS-RM)
- HTTP is typically used as a transport protocol, however, HTTP is an unreliable transport for sending messages. The WS-RM protocol is introduced in the Feature Pack for Web Services to support more reliable message exchange between Web services using HTTP.
- WS-MetadataExchange (WS-MEX)
- In WAS Version 7.0, using JAX-WS, you can enable the Web Services Metadata Exchange (WS-MetadataExchange) protocol so that the policy configuration of the service provider is included in the WSDL and is available to a WS-MetadataExchange GetMetadata request. One advantage of using the WS-MetadataExhange protocol is that you can apply message-level security to WS-MetadataExchange GetMetadata requests by using a suitable system policy set. Another advantage is that the client does not have to match the provider configuration, or have a policy set attached. The client only needs the binding information, and then the client can operate based on the provider policy, or based on the intersection of the client and provider policies.
- WS-Policy
- WAS conforms to the Web services Policy Framework (WS-Policy) specification. You can use the WS-Policy protocol to exchange policies in standard format. A policy represents the capabilities and requirements of a Web service, for example whether a message is secure and how to secure it, and whether a message is delivered reliably and how this is achieved. You can communicate the policy configuration to any other client, service registry, or service that supports the WS-Policy specification, including non-WAS products in a heterogeneous environment.
- Data Web services (replacement for DADX Web services)
- New in v7.5.1 you can use the Data Web Services tools to create Web services that expose database operations (SQL SELECT and DML statements, XQuery expressions, or calls to stored procedures) to client applications. Data Web Services is a next generation solution to significantly ease the development, deployment, and management of Web services-based access to DB2 and IDS database servers. This is a replacement for the DADX and WORF tools available in previous releases. For more information refer to: Developing Data Web Services.
Web services tooling supports the following specifications:
Technology or specification WAS 6.1 without the Feature Pack for Web Services installed WAS 6.1 with the Feature Pack for Web Services installed WAS 7.0 Transports HTTP/HTTPS v1.0 and v1.1 v1.0 and v1.1 v1.0 and v1.1 JMS Supported for JAX-RPC Web services
- Supported for JAX-RPC Web services
- Not supported for JAX-WS Web services
- Supported for JAX-RPC Web services
- Supported for JAX-WS Web services
Messaging SOAP specification v1.1
- v1.1 supported for all Web services
- v1.2 support limited to JAX-WS Web services
- v1.1 supported for all Web services
- v1.2 support limited to JAX-WS Web services
SOAP Attachements SAAJ 1.2 SAAJ 1.2 and 1.3 SAAJ 1.2 and 1.3 SOAP MTOM Not applicable v1.0 support limited to JAX-WS Web services v1.0 support limited to JAX-WS Web services Description UDDI
- Unit Test UDDI wizard creates v3.0 registries
- Web Services Explorer works with v2.0 and v3.0 registries
- Unit Test UDDI wizard creates v3.0 registries
- Web Services Explorer works with v2.0 and v3.0 registries
- Unit Test UDDI wizard creates v3.0 registries
- Web Services Explorer works with v2.0 and v3.0 registries
WSDL v1.1 v1.1 v1.1 WSIL v1.0 v1.0 v1.0 Security WS-Security OASIS Standard 1.0 OASIS Standard 1.1 OASIS Standard 1.1 WS-Addressing Not applicable v1.0 supported for JAX-WS Web services v1.0 supported for JAX-WS Web services WS-RM Not applicable Oasis Standard 1.1 Oasis Standard 1.1 WS-MetadataExchange Not applicable Not applicable Supported Interoperability WS-I Basic Profile 1.1.2 1.1.2 1.1.2, 1.2, 2.0 WS-I Simple SOAP Binding Profile 1.0.3 1.0.3 1.0.3, 1.1 WS-I Attachments Profile 1.0 1.0 1.0 WS-I Basic Security Profile Not applicable 1.0 1.0 Other Standards JAX-RPC
- v1.0 for J2EE 1.3
- v1.1 for J2EE 1.4
- v1.0 for J2EE 1.3
- v1.1 for J2EE 1.4
- v1.0 for J2EE 1.3
- v1.1 for J2EE 1.4
JAX-WS Not applicable v2.0 v2.0, 2.1 JSR 109 and JSR 921
- JSR 109 1.0 - J2EE 1.3
- JSR 921 1.0 - J2EE 1.4
- JSR 109 1.0 - J2EE 1.3
- JSR 921 1.0 - J2EE 1.4
- JSR 109 1.1 - Java EE 5
- JSR 109 1.0 - J2EE 1.3
- JSR 921 1.0 - J2EE 1.4
- JSR 109 1.1 - Java EE 5
- JSR 109 1.2 - Java EE 5
JAXB/JSR-222 Not applicable v2.0 v2.0, v2.1 JSR-181 - Web Services Metadata (Annotations) Not applicable
- v2.0 for JAX-WS Web services
- Not supported for JAX-RPC Web services
- v2.0 for JAX-WS Web services
- Not supported for JAX-RPC Web services
Related concepts
Web Services Description Language (WSDL)
Universal Description, Discovery, and Integration (UDDI)
Web Services Inspection Language (WSIL)
Managing policy sets for Web services and clients