Re: how to bind jaxrs:server to default http service
Ok ... thanks for the info. We've got it working in one instance now but not our 'real' instance ... but this helped us get it forward. Thanks for the response. On Tue, Jun 26, 2012 at 1:56 AM, Freeman Fang freeman.f...@gmail.comwrote: Hi, Yeah, it's possible, as long as your address start with /, which means it will use http-osgi transport(http osgi service provided by paxweb). Generally the port conflict only comes from your address is like http://localhost:8181/blabla..., which means will use http-jetty transport. But from your configuration it's not this case, which CXF version you are using? Double check ensure you're not use http-jetty transport. Freeman On 2012-6-26, at 上午3:24, Vestal, Rick wrote: Hi all, Is it possible to bind a jaxrs:server definition in a blueprint file to the default karaf http service? e.g. whenever I do something like the example below, it fails due to a port conflict with the default service. jaxrs:server id=myREST address=/${archiveRestPath} jaxrs:serviceBeans ref component-id=mybean/ /jaxrs:serviceBeans /jaxrs:server If so, is it possible to even further extend the default service with providers and interceptors? Thanks, -- Rick - Freeman Fang FuseSource Email:f d...@fusesource.comf...@fusesource.com Web: fusesource.com Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: http://weibo.com/u/1473905042
how to bind jaxrs:server to default http service
Hi all, Is it possible to bind a jaxrs:server definition in a blueprint file to the default karaf http service? e.g. whenever I do something like the example below, it fails due to a port conflict with the default service. jaxrs:server id=myREST address=/${archiveRestPath} jaxrs:serviceBeans ref component-id=mybean/ /jaxrs:serviceBeans /jaxrs:server If so, is it possible to even further extend the default service with providers and interceptors? Thanks, -- Rick
labs-paxexam testing strategy question
Hi, We are starting to convert our project over to osgi and are using the labs-paxexam testing mechanism. We have a custom karaf distribution (adds some bundles we need across our projects, logging, etc). I'd like to build a test artifact along with our karaf distribution that contains testing utilities consuming projects can use such that they don't need to rewrite the initialization code if they don't want to. I think this will work ok for @Configuration methods as it is run locally and the standard maven depends mechanisms will pick up the classes just fine, however, if the actual @Test methods use any of these test utilities, then the classes are not available in the karaf distribution. Are there any recommended ways to get a jar of utilities into the karaf distribution when using labs-paxexam such that it is available from the test classes being executed? Thanks, -- Rick