You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/12/06 14:02:29 UTC

[jira] Resolved: (CAMEL-190) Camel transport for CXF

     [ https://issues.apache.org/activemq/browse/CAMEL-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved CAMEL-190.
----------------------------------

    Resolution: Fixed

Patch applied with thanks!

> Camel transport for CXF
> -----------------------
>
>                 Key: CAMEL-190
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-190
>             Project: Apache Camel
>          Issue Type: Sub-task
>          Components: camel-cxf
>            Reporter: Willem Jiang
>             Fix For: 1.3.0
>
>         Attachments: camel-190.patch
>
>
> We could implement an Camel transport for CXF to use.
> In this case, CXF client can easily access the service which is provided by other Camel endpoint.
> BTW, we could save hop by not send the message to the camel-cxf component's consumer.
> To avoid the circlar dependency between the Camel and CXF,  all the Camel transport work will be done in the Camel svn.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.