WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results
             New or updated topic for this feature pack

Invoking one-way JAX-RPC Web service requests transactionally using the JMS transport

Use the enableTransactionalOneWay property to ensure that one-way JAX-RPC Web service requests using the JMS transport will be sent to the destination queue or topic transactionally.

About this task

New or updated for this feature pack Important: The WebSphere Application Server Version 6.1 Feature Pack for Web Services extends the capabilities of this product to introduce support for the Java API for XML-Based Web Services (JAX-WS) 2.0 programming model. JAX-WS is the next generation Web services programming model complimenting the foundation provided by the Java API for XML-based RPC (JAX-RPC) programming model. Using the strategic JAX-WS programming model, development of Web services and clients is simplified through support of a standards-based annotations model. Although the JAX-RPC programming model and applications are still supported, take advantage of the easy-to-implement JAX-WS programming model to develop new Web services applications and clients.
New or updated for this feature pack Supported configurations: The Feature Pack for Web Services does not support Java Message Service (JMS) transports or enterprise beans. This product only supports an HTTP transport and hosting JavaBeans endpoints within the Web container for JAX-WS Web services applications. To develop enterprise beans hosted as Web services, you must use the JAX-RPC programming model. This product does allow JAX-WS clients to issue requests from any of the Java Platform, Enterprise Edition (Java EE) containers along with the client Java 2 Standard Edition (J2SE) environment.sptcfg

The enableTransactionalOneWay property is applicable for WebSphere Application Server V6.0.2 Service Release 9 and later.

When using JMS to transport Web service requests, the default behavior is for the SOAP message to be added to the destination queue or topic non-transactionally or outside of the client application's transaction. Adding the SOAP message to the destination queue or topic is done outside of the transaction to avoid synchronization problems that can occur with two-way Web service requests. However, you can choose to allow one-way requests to be processed as part of the transaction. The enableTransactionalOneWay property can be used to ensure that one-way Web service requests that use the JMS transport will be sent to the destination queue or topic transactionally. When the client application invokes the one-way Web service request, the resulting SOAP request message is added to the destination queue or topic as part of the client application's transaction.

Use one of the following ways to enable the enableTransactionalOneWay property.

Procedure

Results

You have a Web service client application that is configured to invoke one-way requests transactionally while using the JMS transport.

What to do next

After you have enabled the enableTransactionalOneWay property, run the client application.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twbs_jmsonewayreq.html