You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/11/07 15:19:00 UTC
[jira] [Commented] (QPID-5080) Allow Qpid JCA adapter to provide
for alternate ConnectionFactory Implementations
[ https://issues.apache.org/jira/browse/QPID-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242167#comment-16242167 ]
Keith Wall commented on QPID-5080:
----------------------------------
JCA was removed by QPID-7716, so making this JIRA Won't Fix.
> Allow Qpid JCA adapter to provide for alternate ConnectionFactory Implementations
> ---------------------------------------------------------------------------------
>
> Key: QPID-5080
> URL: https://issues.apache.org/jira/browse/QPID-5080
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client, JCA
> Affects Versions: 0.22
> Environment: All supported OS platforms, all supported JEE platforms.
> Reporter: Weston M. Price
> Assignee: Weston M. Price
> Priority: Minor
> Fix For: Future
>
>
> Currently the Qpid JCA adapter assumes the AMQConnectionFactory is the solve provider for JMS connectivity. The adapter should be modified to allow for different CF implementations based on environment etc.
> Note, this modification should allow for the outbound and inbound connections to use a different CF as warranted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org