Current Camel Jetty component doesn’t support to share the Jetty component across bundle. So I think if you put two bundles which use the same port into OSGi container, you will Socket bind error.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 20, 2013 at 4:17:09 AM, samslara (samsl...@yahoo.com) wrote: > > Hello, > I have a question about the behavior of the jetty component when > in an > OSGi environment (such as in ServiceMix). If I have two bundles > each with a > camel context where one has a route such as: > > > ... > > and the other has a route such as: > > > ... > > and I call the container with > > http://:8080/application1/a/b/c > > Because of the overlapping url but with the second route being > more specific > will this request go to the 2nd route, the 1st route, randomly > to either or > will something else occur? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Jetty-component-and-overlapping-urls-when-a-consumer-tp5745068.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
