You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2007/10/23 10:04:23 UTC
[jira] Created: (CAMEL-190) Camel transport for CXF
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
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.
[jira] Commented: (CAMEL-190) Camel transport for CXF
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40791 ]
Willem Jiang commented on CAMEL-190:
------------------------------------
Hi James,
I am working on this JIRA and the camel conduit can work now,
If everything is OK , I can submit the patch tomorrow.
Regards,
Willem.
> 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
>
>
> 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.
[jira] Commented: (CAMEL-190) Camel transport for CXF
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40790 ]
James Strachan commented on CAMEL-190:
--------------------------------------
Is this issue still open? Just wondered if we can close it yet with all the CXF effort lately
> 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
>
>
> 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.
[jira] Resolved: (CAMEL-190) Camel transport for CXF
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CAMEL-190) Camel transport for CXF
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CAMEL-190:
-------------------------------
Attachment: camel-190.patch
Implementingthe cxf transport API with Camel core,
also adding the unit test for test camel transport.
TODO
support load camel context in camel transport from spring configuration.
Adding systest and example to show how to use camel transport.
I will fill new camel JIRAs to trace the upper works.
> 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.