Achim: We¹re in a transitional phase right now. OSGI is replacing 4 different home-grown plugin systems to become the modular framework for future development. In time we will have everything within the OSGI container, but that time is not now.
JB: We do use Pax-Web in our Thick Client applications (Swing, SWT). There embedded browser components within those applications display web content served from the OSGI container. This is the primary reason why I need to know the URL of the Http Service. Our Server offering runs in any J2EE application server. We maintain an embedded Karaf instance there with the HttpService bridged out to the outside Servlet Container (primarily Tomcat). I know some people proxy out to PAX-Web, but this won¹t work for us. -Nick On 11/17/14, 1:35 PM, "Jean-Baptiste Onofré" <[email protected]> wrote: >Hi Nick, > >why not just using Pax Web ? > >Pax Web register the servlet as service, so you can do a simple lookup. > >Regards >JB > >On 11/17/2014 04:34 PM, Nick Baker wrote: >> Hey All, >> >> I¹ve got a mixed environment where a Bundle can be deployed in an >> environment using the standard PAX-Web HttpService as well as one >> bridging out to Tomcat by way of Felix-HTTP Bridge. I need to be able to >> programmatically determine the URL for the HttpService regardless of >> where a bundle is deployed. There doesn¹t seem to be any way of >> determining this using the standard OSGI APIs. >> >> Karaf is embedded within both environments. The PAX-Web setup will >> dynamically find an open port on startup and set the appropriate >> Configuration Admin entries before starting Karaf. The Tomcat >> environment does not need to do this work. >> >> Any ideas appreciated, >> -Nick > >-- >Jean-Baptiste Onofré >[email protected] >http://blog.nanthrax.net >Talend - http://www.talend.com
