+

Search Tips   |   Advanced Search

Frequently asked questions about Web services


This page presents frequently asked questions about the development and implementation of Web services.

 

What is the relationship of the WebSphere product to Apache open source?

The WebSphere product has always extensively supported open source. From a Web services perspective, the WebSphere product contributes a large percentage of the JAX-RPC spec to the open source Apache Axis community.

WebSphere Community Edition uses the Apache Axis runtime for its support for JAX-RPC 1.1. With the movement of Web services to a more messaging-centric asynchronous model, the Apache Axis community has created a new version of a Web services runtime that is based on the StAX architecture entitled Axis2.

Axis2 introduces its own proprietary programming and deployment model that is agnostic of any Java -based JCP standards. It did this primarily so that it could support multiple Java -based models, whether it JAX-WS, SCA (Apache Tuscany) and Groovy. While the application server implements a standards-based JAX-WS model, it actually uses a version of Axis2 as part of its implementation. We might see messages during tracing or within call stacks that reflect its Axis2 origins. The WebSphere product is supporting only the JAX-WS model and the deployment model that is documented in the information center. Any usage of native Axis2 APIs is not supported by the WebSphere product.

 

What IBM development tools work with Web Services?

The Rational Application Developer assembly tools provide a graphical interface for developing code artifacts, assembling the code artifacts into various archives or modules, and configuring related Java EE deployment descriptors.

 

Is Web Services for Java EE technology part of the Java EE specification?

WAS Version 7.0 and later is based on Web Services for Java EE 5. Prior to Java EE 5, the spec name was J2EE. WAS V6.x is based on J2EE 1.4. For WAS Version 5.0.2 and V5.1.x, the Web Services for J2EE V 1.0 spec is an addition to J2EE 1.3. The J2EE specification 1.4 requires support for Web Services for J2EE V1.1. Minor differences exist between the J2EE 1.3 V(JSR-109 V1.0) and the J2EE 1.4 V(JSR-109 V1.1).

 

What standards does the Web services run time support?

We can review the standards and specifications that are supported by WAS for the Web services run time in Specifications and API documentation.

 

Does the Web Services for Java EE technology interoperate with other SOAP implementations, like .NET?

WAS supports Web services that are consistent with the WS-I Basic Profile, and should interoperate with any other vendor conforming to this specification.

 

Can I use a Java Beans component to implement a Web service using SOAP over JMS invocation?

The SOAP over JMS support provides access only to enterprise beans-based Web services To use a Java Beans implementation instead of an enterprise bean to implement the service endpoint, create a facade enterprise bean that delegates to the Java Beans implementation.

 

Does the SOAP over JMS support interoperate with other vendors?

Before WAS Version 7.0, no spec has existed that describes interoperability requirements for SOAP over JMS implementations. WAS V7.0 introduces support for the emerging industry standard SOAP over Java Message Service specification. This proposed standard provides a standard set of interoperability guidelines for using a JMS-compliant transport with SOAP messages to enable interoperability between the implementations of different vendors. Support for this emerging standard positions WebSphere to be able to interoperate with other vendor implementations of SOAP over JMS as this standard is adopted. While the spec is in draft form and not yet final, WAS V7.0 supports the current SOAP over JMS draft specification. To learn more about this specification, see the specifications and API documentation.

 

How does two-way messaging with a SOAP and JMS implementation work? Can it support multiple clients making simultaneous requests?

When using two-way Web services operations, the client can choose to use a permanent reply queue or the Web services run time will, by default, use a temporary JMS queue. When the client issues a two-way request, the underlying Web services run time creates a temporary JMS queue, if a permanent queue is not being used, to receive the response. The reply queue, either temporary or permanent, is specified as the replyTo destination that is in the outgoing JMS request message. After the server processes the request, it directs the response to the replyTo destination specified in the request message. The client deletes the temporary queue, if a permanent queue was not used, after the response is received. The server can handle simultaneous requests from multiple clients because each incoming request message contains the destination to which the reply is sent.



 

Related tasks


Troubleshooting Web services

 

Related


Web services specifications and APIs