JAX-WS JMS transport works on a JMS server by using the ConnectionFactory and Destination properties of the server. JAX-WS JMS transport uses a queue type as a Destination. A <connection-factory and <destination> properties must be configured in the domain.xml file on the JEUS MQ server. Refer to "JEUS MQ Guide" for detailed information about the configuration.

The following is an example of configuring JAX-WS JMS transport.

<jms-engine xmlns="http://www.tmaxsoft.com/xml/ns/jeus">
    ...
    <connection-factory>
        <type>queue</type>
        <name>QueueConnectionFactory</name>
        <service>jmstest</service>
    </connection-factory>
    ...
</jms-engine>
<jms-resource>
    ...
    <destination>
        <type>queue</type>
        <name>ExamplesQueue</name>
        <multiple-receiver>true</multiple-receiver>
    </destination>
    ...
</jms-resource>

To use JMS transport instead of HTTP, add the @jeus.webservices.jaxws.api.JMSWebService annotation to the web service endpoint.

The following is a web service endpoint that includes the @JMSWebService annotation.

@WebService
@jeus.webservices.jaxws.api.JMSWebService(
    jndiConnectionFactoryName = "QueueConnectionFactory",
    destinationName = "ExamplesQueue",
    targetService = "AddNumbersImplService")
public class AddNumbersImpl {
...

The following are the JMS WebService properties.

To create a web service endpoint from WSDL, a wsdl:port for JMS transport and a wsdl:port that uses HTTP must be configured in the WSDL of the deployed application (WAR or JAR).

The following is an example of specifying JMS URI in wsdl:port's soap:address for JAX-WS JMS transport in WSDL.

<definitions name="AddNumbers" targetNamespace="urn:AddNumbers" ... >
    ...
    <service name="AddNumbersService">
    <port name="AddNumbersPort" binding="impl:AddNumbersBinding">
        <soap:address location="http://<host>:<port>/<context>/AddNumbersService" />
    </port>
    <port name="AddNumbersJMSPort" binding="impl:AddNumbersBinding">
        <soap:address location="jms:jndi:ExamplesQueue?targetService=AddNumbersImplService&jndiConnectionFactoryName=QueueConnectionFactory" />
    </port>
    </service>
</definitions>

A <port name> in wsdl:port for JMS transport must be identical to the @JMSWebService#portName property value of the web service endpoint.

SOAP/JMS' JMS URI must be specified according to the 'SOAP over Java Message Service 1.0' standard.

JMS URI uses the "jms" scheme, and specifies the destination name to query JMS destination with JNDI.

JMS URI's targetService property must be identical to the web service endpoint's @JMSWebService#targetService property value.

A web service client that uses JAX-WS JMS transport can call a web service through JMS by using a JMS port instead of the existing HTTP port.

The published WSDL of the web service has the wsdl:port information that is used for JMS transport. A service class that extends javax.xml.ws.Service created from the WSDL through the wsimport tool has a method for obtaining a JMS port, and one for obtaining the existing HTTP port.

As shown in the following example, a web service client application can invoke a web service by selecting a port type.

//AddNumbersPortType port = new AddNumbersService().getAddNumbersPort();
AddNumbersPortType port = new AddNumbersService().getAddNumbersJMSPort();
...