You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "willem Jiang (JIRA)" <ji...@apache.org> on 2007/01/04 10:57:27 UTC

[jira] Commented: (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:comment-tabpanel#action_12462177 ] 

willem Jiang commented on CXF-318:
----------------------------------

Current CXF JMS demo just need the JMS API jar for build, and we write the build.xml to look for the API jar from ActiveMQ. 
For Qpid I think we just need to update the readme file. That can tell the people if they want to use Qpid, they just need to update the wsdl for the Jndi and jms broker stuff.


> 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
>            Reporter: Suresh Kodichath
>         Attachments: CXF_Qpid_support_JMS.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira