Your proposed way sounds pretty good, it's also possible to bind your web-services to the Karaf contained Pax-Web container, but I'm not sure if it already supports to bind every endpoint to a different connector. So I think you're on a safe road there.
regards, Achim 2013/6/4 m.mcinness1 <[email protected]> > 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. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/>
