[
https://issues.apache.org/jira/browse/CXF-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633799#action_12633799
]
Christian Schneider commented on CXF-1806:
------------------------------------------
I would use the correlation ID to idnetify the pair but my colleague Eduard
told me there could be an Interceptor that does the correlation already. So I
thought that I perhaps could simply put the reponse in a chain and it is
correlated by CXF. If this is not implemented elsewhere I will implement it.
For the jndi case I have already included the folowing code:
ConnectionFactory connectionFactory =
(ConnectionFactory)jt.lookup(connectionFactoryName);
UserCredentialsConnectionFactoryAdapter uccf = new
UserCredentialsConnectionFactoryAdapter();
uccf.setUsername(userName);
uccf.setPassword(password);
uccf.setTargetConnectionFactory(connectionFactory);
SingleConnectionFactory scf = new SingleConnectionFactory();
scf.setTargetConnectionFactory(uccf);
So we should already cover the case of a Factory that does not allow
username/password config and the caching of the connection. I hope this is what
you meant Willem?
If later the configuration is done directly by injecting a JMSTemplate then I
would not do anything. In this case I would suggest to simply write a Howto
that describes how to do the same as above in a spring config.
> 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.
