camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2389) Split camel transport for cxf out of camel-cxf module
Date Sat, 23 Jan 2010 11:00:44 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57080#action_57080
] 

Christian Schneider commented on CAMEL-2389:
--------------------------------------------

Hi Willem,

after thinking a little more about cxfbean it is probably not so bad if only for some users.
If I understand it correctly it tries to figure out which frontend to use by looking at the
bean to proxy and then wires the frontend to the transport.

I think it could be implemented better though perhaps with some help from the cxf project.
The one place in cxfbean that is problematic is CxfBeanEndpoint.createServer. There JaxWsServerFactoryBean
orJAXRSServerFactoryBean are explicitly created. Perhaps this could be done in cxf. Cxf could
offer an API function to create a frontend for a bean by inspecting it. The implementation
could go through the loaded frontends and decide which to use. So the camel part only needs
to call a well known API function of CXF. This could be a solution for Camel 3.0.

Btw. my second patch still seems to have some flaws. I found that some CxfConstants also need
to be moved. Interestingly structure101 did not see this. I guess because the constants are
defined in an interface. Honestly I must say I also never saw constants being defined in this
way before ;-)


> 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.


Mime
View raw message