Hi, Though use standalone http-jetty transport would work, in OSGi container we suggest to use http-osgi transport(which is use osgi http service provided by pax-web), one port configuration is easier for you to manage(like the firewall configuration, etc). Think about you deploy multiple wars into a tomcat container, every user only expect one well known listening port, right? ------------- Freeman(Yue) Fang
Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 www.camelone.org : The open source integration conference: On 2013-6-5, at 上午1:00, m.mcinness1 wrote: > I'm using Karaf 2.2.4 with Servicemix 4.4.2. In configuring jaxrs with > blueprint, I am finding it convenient to define multiple servers as jetty > endpoints, with each jaxrs server listening on a different port (please see > below) > > Is there anything wrong or bad or misguided about this configuration or > deploying multiple bundles with multiple jetty/jaxrs resources in Karaf? I > guess I'm fishing for advice on best practices. > > Thanks for any insight or guidance. > > Bundle A, blueprint excerpt: > > <jaxrs:server id="abc" address="https://0.0.0.0:18001"> > <jaxrs:serviceBeans> > <bean class="com.something.resources.Resource" /> > </jaxrs:serviceBeans> > <jaxrs:inInterceptors> > <ref component-id="securityInterceptor"/> > </jaxrs:inInterceptors> > </jaxrs:server> > > <jaxrs:server id="xzy" address="http://0.0.0.0:18002"> > <jaxrs:serviceBeans> > <bean class="com.something.resources.Resource" /> > </jaxrs:serviceBeans> > </jaxrs:server> > > Bundle B, bluepring exerpt > > <jaxrs:server id="123" address="http://0.0.0.0:18101"> > <jaxrs:serviceBeans> > <bean class="com.something.resources.Resource" /> > </jaxrs:serviceBeans> > </jaxrs:server> > > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Jetty-and-multiple-jaxrs-servers-tp4028957.html > Sent from the Karaf - User mailing list archive at Nabble.com.
