[
https://issues.apache.org/jira/browse/CAMEL-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042666#comment-13042666
]
Willem Jiang commented on CAMEL-2389:
-------------------------------------
Hi Christina,
The main reason that I want to pull out the camel transport from camel-cxf
module is I don't want the camel-cxf depends on camel-cxf-transport.
As the camel-cxf should no know nothing about the transport detail.
current camel-cxf-transport only share some class with camel-cxf, such as the
CXFMessageHeaderFilter and the header helper class.
If you are comfortable camel-cxf-transport dependent on camel-cxf, we may think
about add a new CXFMessageHeaderFilter and message helper class into
camel-cxf-transport module.
> Split camel transport for cxf out of camel-cxf module
> -----------------------------------------------------
>
> Key: CAMEL-2389
> URL: https://issues.apache.org/jira/browse/CAMEL-2389
> Project: Camel
> Issue Type: Task
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.8.0
>
> Attachments: camel-cxf-2010-01-22.patch, camel-cxf-2010-01-23-with
> base.patch, camel-cxf-after-patch2.png, camel-cxf-after.png,
> camel-cxf-before.png
>
>
> As camel-transport for cxf independents from the cxf-rs and cxf component, we
> need to put it into other module to avoid unnecessary third party dependency.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
