[
https://issues.apache.org/activemq/browse/CAMEL-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57078#action_57078
]
Willem Jiang commented on CAMEL-2389:
-------------------------------------
Hi Christian,
If we treat the cxf-transport-camel is a way to deploy the camel context into
CXF container, the cxfbean is a way to deploy CXF service impl into the Came.
Compare the cxf-transport-camel, the cxfbean provides a easy way that user
don't need to touch the CXF transport configuration for the camel user who
don't familiar with the CXF transport configuration.
I just take a look at cxfbean package, found it dependents on the
CamelDestination which is a part of camel cxf transport.
My plan is removing the CXF soap component first as we barely use it, then we
can clean up the cxf-transport-camel a litter bit.
But consider the backward compatible, we may do it in sandbox first and
release it in Camel 3.0.
> Split camel transport for cxf out of camel-cxf module
> -----------------------------------------------------
>
> Key: CAMEL-2389
> URL: https://issues.apache.org/activemq/browse/CAMEL-2389
> Project: Apache Camel
> Issue Type: Task
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: Future
>
> 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.
-
You can reply to this email to add a comment to the issue online.
