camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] Commented: (CAMEL-2389) Split camel transport for cxf out of camel-cxf module
Date Sat, 23 Jan 2010 08:30:48 GMT


Christian Schneider commented on CAMEL-2389:

How about creating a new component cxf-camel-transport or some similar name. We move the packages
transport and transport.spring to the new component. Then we add a dependency from camel-cxf
to the new component. 

So people who use camel-cxf like before simply include camel-cxf and have all features. In
fact I think they will not even notice somthing has changed. Someone who only wants the transport
will only depend on the new component and have much less dependencies.

If you want to completely remove the dependency between camel-cxf and the new component you
probably need a common base lib that both depend on. Currently CxfHeaderFilterStrategy, CxfHeaderHelper,
SoapMessageHeaderFitler, MessageFilter and CXFSoapBinding seem to be the common classes needed
by transport and cxf packages. I think it makes sense to already have a package for these
classes. I will attach a new patch that implements this.

I first thought we could also move the cxfbean package to the new component project. In structure
101 it seems to depend only on transport. This not possible though as it directly references
JaxWsServerFactoryBean and JAXRSServerFactoryBean. Honestly I think we should completely remove
the cxfbean component and package in the long run. In my opinion it has practically no advantages
compared to the camel transport and it creates very ugly dependencies that are better handled
by spring. I will also ask this on the mailing list and try to get some opinions. 

> Split camel transport for cxf out of camel-cxf module
> -----------------------------------------------------
>                 Key: CAMEL-2389
>                 URL:
>             Project: Apache Camel
>          Issue Type: Task
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: Future
>         Attachments: camel-cxf-2010-01-22.patch, 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.

View raw message