You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Faisal Masood (JIRA)" <ji...@apache.org> on 2015/03/26 00:39:53 UTC

[jira] [Commented] (CAMEL-5884) camel-cxf - Allow to define which operationNames a given consumer services

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

Faisal Masood commented on CAMEL-5884:
--------------------------------------

We actually have this problem in of the projects I was doing. In the end, I created a gateway route, which then on the basis of operation names further route to other routes. I made everything configurable so that names of other routes and transport also become customisable. One thing though, I had to write an intercetptor to fetch the soap operation name. This all thing can be done in the cxc component and i am happy to take this lira.

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