cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] Commented: (CXF-1806) Use Spring JMSTemplate in JMSConduit instead of direct JMS
Date Wed, 24 Sep 2008 07:05:47 GMT


Willem Jiang commented on CXF-1806:

cool, the connection factory is  what I concerned. 

Here are some comments for the correlation ID.  AFAIK, I don't think there is an interceptor
which correlates the message by using the correlation ID.
 I think the correlation ID is a transport level (physical) thing, and the interceptors are
doing some logical  things. eg. correlation ID is useless for the http transport.
We put the all the context staffs in the message or exchange , and don't use any member objects
of the interceptor to make sure the interceptor is  thread safe.  It not easy to do the correlation
work in the interceptor.

> Use Spring JMSTemplate in JMSConduit instead of direct JMS
> ----------------------------------------------------------
>                 Key: CXF-1806
>                 URL:
>             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.

View raw message