axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (AXIS2-1665) JMS destination should not be dedicated to only a single service
Date Mon, 11 Jun 2007 19:13:26 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Deepal Jayasinghe reassigned AXIS2-1665:
----------------------------------------

    Assignee: Asankha C. Perera  (was: Sanka Samaranayake)

Hi Asankha,
Could you please have a look at this.

> JMS destination should not be dedicated to only a single service
> ----------------------------------------------------------------
>
>                 Key: AXIS2-1665
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1665
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: transports
>         Environment: Not important
>            Reporter: Ali Sadik Kumlali
>            Assignee: Asankha C. Perera
>            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/axis-dev@ws.apache.org/msg24261.html

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message