You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2009/10/16 21:23:31 UTC
[jira] Resolved: (CXF-318) Support for using Apache Qpid as a CXF
transport.
[ https://issues.apache.org/jira/browse/CXF-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-318.
-----------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
Assignee: Daniel Kulp
I'm marking this resolved. The demo readme's have been updated to talk about how to use QPid (and other JMS providers). Since QPid is a JMS provider. We use standard JMS things (actually, Spring JMS) which should allow interop with any compliant JMS provider. We cannot test them all.
> Support for using Apache Qpid as a CXF transport.
> -------------------------------------------------
>
> Key: CXF-318
> URL: https://issues.apache.org/jira/browse/CXF-318
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Affects Versions: 2.0-RC
> Reporter: Suresh Kodichath
> Assignee: Daniel Kulp
> Fix For: Invalid
>
> Attachments: CXF_Qpid_support_JMS.patch, DemoReadMeChangesForQpid.patch, DemoReadMeChangesForQpid.patch
>
>
> Hi,
> This story is to add support for using Apache Qpid as a transport for CXF. Apache Qpid provides a JMS interface as well as a Native interface. This story is to use the existing JMS transport in CXF, and make it work for Qpid along-with the necessary tests and demos for the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.