[
https://issues.apache.org/jira/browse/TUSCANY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530287
]
Simon Laws commented on TUSCANY-1806:
-------------------------------------
Ok, sounds like a plan. So looking at you changes you are already getting hold
of the transport description. Are you saying you could potentially add the JMS
one at this stage if one has not been specified in axis.xml and have Axis
process it or is it too late?
Regards
Simon
> Support for SOAP over JMS in Axis binding
> -----------------------------------------
>
> Key: TUSCANY-1806
> URL: https://issues.apache.org/jira/browse/TUSCANY-1806
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-1.0, Java-SCA-1.0.1
> Reporter: dinesh shahane
> Assignee: Simon Laws
> Attachments: tuscany_1.0_binding-ws-axis2_soap_jms_TUSCANY-1806.diff
>
>
> Axis2 binding currently supports SOAP over HTTP, a simple SOAP/JMS support
> could be added using the Axis2 functionality. The following email thread has
> information about the proposed enhancements.
> http://www.mail-archive.com/[email protected]/msg20760.html
> Attached patch file has support for SOAP/JMS along with samples containing
> service and reference. This patch modifies axis2.xml and Axis2ServiceProvider
> class to create a SOAP/JMS service based on specified @wsdl.port and
> @uri/@wsdl.binding in <binding.ws> element. Currently it doesn't support
> EndpointReference or extensibility elements as discussed in the email thread.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
