You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Weston M. Price (JIRA)" <ji...@apache.org> on 2013/01/04 16:18:13 UTC
[jira] [Resolved] (QPID-4318) QpidConnectionFactoryProxy should
implement Queue/Topic Connection factory API's to support older clients
[ https://issues.apache.org/jira/browse/QPID-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weston M. Price resolved QPID-4318.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.19)
0.21
Trunk contains the current fix for this issue as well as a new simple system test for connectivity, interface support etc.
> QpidConnectionFactoryProxy should implement Queue/Topic Connection factory API's to support older clients
> ---------------------------------------------------------------------------------------------------------
>
> Key: QPID-4318
> URL: https://issues.apache.org/jira/browse/QPID-4318
> Project: Qpid
> Issue Type: Improvement
> Components: JCA
> Affects Versions: 0.18
> Environment: All supported OS platforms, all supported JEE platforms.
> Reporter: Weston M. Price
> Assignee: Weston M. Price
> Priority: Minor
> Fix For: 0.21
>
>
> Currently the QpidConnectionFactoryProxy only implements the javax.jms.ConnectionFactory API. We are seeing issues in varying JEE environments where certain containers depend on the ConnectionFactory implementing either Queue or Topic connection factory. In order to address this, the ConnectioFactoryProxy should implement the messaging domain specific API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org