You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2007/11/21 09:36:27 UTC
[jira] Commented: (SM-1133) verify how camel is used as core of
jax-ws process
[ https://issues.apache.org/activemq/browse/SM-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40670 ]
Willem Jiang commented on SM-1133:
----------------------------------
One more thing for the pojo with a soap annotation supporting , we need to figure out a way to share the service model ( some kind of WSDL information) between the smx:endpoint and soap:http:xxx .
> verify how camel is used as core of jax-ws process
> --------------------------------------------------
>
> Key: SM-1133
> URL: https://issues.apache.org/activemq/browse/SM-1133
> Project: ServiceMix
> Issue Type: Sub-task
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 4.0
>
>
> As Guillaume point out
> we should split the soap processing with the pojo invocation, as in jbi with the bc/se, to reuse most of the existing code, we could easily reusecode from either the cxf se/bc, or the camel cxf support
> for the end user, if you deploy a pojo with a soap annotation, it would be exposed both internally and externally (using some kind of BC)
> if we reuse the camel -> servicemix bridge, it should be easy to do both part
> from("soap:http:xxx).to("smx:the-endpoint") for the BC part
> from("smx:the-endpoint").to("cxf:the-bean") for the SE part
> This task need verify how camel play as the core of this process, maybe an integration test is needed here
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.