Force Deployment Over JMS Transport Only
If not explicitly configured, a web service is deployed over all activated transports in Web Services Stack. However, you can restrict a web service to be deployed over JMS transport only. You can also specify the destination where the service listens for messages, as well as the name of the connection factory to be used. The service can use one of the connection factories defined within the JMS transport receiver in the axis2.xml configuration file.
Do one of the following:
Configure the web service’s services.xml file by adding the <transport>jms</transport> element:
<service ...>
<transports>
<transport>jms</transport>
</transports>...
</service>
Use the
Web Services Stack plug-in to
Software AG Designer at deployment time by selecting
JMS Transport from the list of transports in the
Services tab.
