Verifying WSDL syntax compliance for JMS services

Various Java™ Message Service (JMS) providers vary in the syntax used for describing services. Before testing JMS services, you must ensure that Web Services Description Language (WSDL) files comply with the requirements of the tool.

Procedure

  1. In the project explorer or test explorer, locate and open the WSDL file for the JMS service that you want to test. If necessary, you can import a WSDL file from the file system by clicking File > Import > File System.
  2. Ensure that the following criteria are met in the syntax of the WSDL file that you use.
    • Namespace: xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
    • SOAP bindings are set to: transport="http://schemas.xmlsoap.org/soap/jms"
    • JMS transports are defined either as a URL or as jms:address element
  3. If the WSDL file is not compliant, edit the file so that it meets the criteria, and then save and close the file.

Example

For example, a JMS defined as a URL looks like this:
<soap:address location="jms:/queue?jndiConnectionFactoryName=UIL2ConnectionFactory;
             jndiDestinationName=queue/testQueue;
             initialContextFactory=org.jnp.interfaces.NamingContextFactory;
             jndiProviderURL=9.143.104.47"/>
A JMS defined as an address looks like this:
<jms:address destinationStyle="queue" 
             jndiConnectionFactoryName="myQCF"
             jndiDestinationName="myQ"
             initialContextFactory="com.ibm.NamingFactory" 
             jndiProviderURL="iiop://something:900/">
</jms:address>
Related concepts:
Service testing guidelines
Service testing overview
Related tasks:
Recording a service test with the generic service client
Recording a service test through a client program
Creating a service test from a BPEL model
Creating a service test manually
Creating a service test for WebSphere MQ
Creating a service test for a plain XML call
Changing service test generation preferences

Feedback