JMS destination should not be dedicated to only a single service
----------------------------------------------------------------
Key: AXIS2-1665
URL: http://issues.apache.org/jira/browse/AXIS2-1665
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: transports
Environment: Not important
Reporter: Ali Sadik Kumlali
Priority: Minor
I'm creating this issue to address the improvements of JMS destination usage
discussed in the axis-dev [1].
Here is the summary:
Requirements
---------------------------------------------------
- A single destination can be used for messages of different services
- Multiple destinations can be used for messages of the same service
Proposal
---------------------------------------------------
At client side:
- Including the service name in the EPR (JMS URL)
- Adding service name to the JMS message header before sending it (the same
approach used for transferring SOAPAction)
At service side:
- Setting "to" field of the MC to the value of service name field retrieved
from JMS message header.
- Setting "soapAction" field of the MC to the value of SOAPAction field
retrieved from JMS message header (this is already done with the current
implementation).
Advantages of the proposal
---------------------------------------------------
- Being more consistent with the other tranports, as all of them include
service name to EPR
- No need for an association between destination and service, thus no need
destination-service association in services.xml
- Being able to use a single destination for multiple services
- Being able to dispatch messages come from different destionations to the same
service
[1] http://www.mail-archive.com/[email protected]/msg24261.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
