[
https://issues.apache.org/jira/browse/CXF-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633631#action_12633631
]
Freeman Fang commented on CXF-1806:
-----------------------------------
Hi Christian,
+1 to use async way for jms transport.
How about use the correlationID to indentifay the request/reponse pair?
Regards
Freeman
> Use Spring JMSTemplate in JMSConduit instead of direct JMS
> ----------------------------------------------------------
>
> Key: CXF-1806
> URL: https://issues.apache.org/jira/browse/CXF-1806
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.1.2
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 2.1.3
>
> Attachments: CXF-1806-2.patch, CXF-1806.patch
>
>
> Using the Spring JMSTemplate has many advantages compared to directly using
> the JMS API. For example cxf services can participate in Transactions.
> The goal for this issue is to replace JMS API in JMSConduit with JMSTemplate
> calls. Additionally the JMSConduit should be made more dependency injection
> friendly. It should not retrieve configuration from the Spring config.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
