8-2 Programming Advanced Features of JAX-RPC Web Services for Oracle WebLogic Server
For each transport that you specify, WebLogic Server generates an additional port in the WSDL. For this reason, if you want to give client applications a choice of transports
they can use when they invoke the Web service JMS, HTTP, or HTTPS, you should explicitly add the transports using the appropriate JWS annotations or child elements
of jwsc.
8.2 Using JMS Transport Starting From Java: Main Steps
To use JMS transport when starting from Java, you must perform at least one of the following tasks:
■
Add the WLJmsTransport annotation to your JWS file.
■
Add a WLJmsTransport child element to the jwsc Ant task. This setting overrides the transports defined in the JWS file.
The following procedure describes the complete set of steps required so that your Web service can be invoked using the JMS transport when starting from Java.
Note: Using JMS transport is an added-value WebLogic feature;
non-WebLogic client applications, such as a .NET client, may not be able to invoke the Web service using the JMS port.
Note: Because you might not know at the time that you are coding
the JWS file which transport best suits your needs, it is often better to specify the transport at build-time using the WLJmsTransport
child element.
Note: It is assumed that you have created a basic JWS file that
implements a Web service and that you want to configure the Web service to be invoked using JMS. It is also assumed that you have set
up an Ant-based development environment and that you have a working build.xml file that includes targets for running the jwsc
Ant task and deploying the service. For more information, see Getting Started With JAX-RPC Web Services for Oracle WebLogic Server.
Table 8–1 Steps to Use JMS Transport Starting From Java
Step Description
1 Configure the WebLogic
Server domain for the required JMS components.
See Section 8.4, Configuring the Host WebLogic Server Instance for the JMS
Transport Web Service .
2 Add the WLJmsTransport
annotation to your JWS file. Optional
This step is optional. If you do not add the WLJmsTransport annotation to your JWS file, then you must add a WLJmsTransport child element to
the jwsc Ant task, as described in Step 3. See
Section 8.5, Using the WLJmsTransport JWS Annotation .
3 Add a WLJmsTransport
child element to the jwsc Ant task. Optional
Use the WLJmsTransport child element to override the transports defined in the JWS file. This step is required if you did not add the
WLJmsTransport annotation to your JWS file in Step 2. Otherwise, this
step is optional. See
Section 8.6, Using the WLJmsTransport Child Element of the jwsc Ant Task
for details.
Using JMS Transport as the Connection Protocol 8-3
See Section 8.8, Invoking a WebLogic Web Service Using JMS Transport
for information about updating your client application to invoke the Web service using
JMS transport.
8.3 Using JMS Transport Starting From WSDL: Main Steps
