[
https://issues.apache.org/jira/browse/CAMEL-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-5884:
-----------------------------------
Assignee: Willem Jiang
> camel-cxf - Allow to define which operationNames a given consumer services
> --------------------------------------------------------------------------
>
> Key: CAMEL-5884
> URL: https://issues.apache.org/jira/browse/CAMEL-5884
> Project: Camel
> Issue Type: New Feature
> Components: camel-cxf
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Fix For: Future
>
>
> Currently when using a cxf consumer in a route, then all the operations is
> serviced by this route.
> This may confuse some people. As well some may want one route per operation.
> We should look into how we can support this.
> Today people would need to use the recipient list and direct endpoints to
> suport this. But many people dont know about this. See this example:
> http://camel.apache.org/cxf-tomcat-example.html
> I guess this is not so easy, as you would then have mutliple routes with the
> same CXF "webservice". But we would like to have this level of indirection.
> And then I guess if a operation name is not bound to any route, then a soap
> fault should be thrown. Or we should allow to let Camel fail on startup
> saying that operation XXX is not bound to any consumer/route. Or something
> like that. Or allow people to turn this on|off.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
