Hi Lars, There is a bug currently that prevents the component from resolving a "match any" consumer endpoint with a bridged producer. I have opened a ticket a provided a patch. You can follow the details here:
https://issues.apache.org/jira/browse/CAMEL-5458 Until then, I believe you can configure your base external endpoint with a context path and then match off of that. I believe this will work as you are expecting. sully6768 On Jul 21, 2012, at 11:03 AM, helander <leh...@gmail.com> wrote: > Hi Sully and thanks for the input. > > Now I think I know how it works, but I have an additional question: > > Both entries in the config file specifies "http://localhost:8181", is it > possible do something like: > > "http://localhost:8181/system/console" on one and > "http://localhost:8181/cxf" on the other > > in order to filter what gets received from the respective jetty port? Or > could you do that kind of filtering > in some other way? > > /Lars > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/cxfEndpoints-and-different-transports-http-https-using-PAX-Web-tp5716216p5716310.html > Sent from the Camel - Users mailing list archive at Nabble.com.