Broadly speaking, there are three configurations for using OSGi on a server:
Native— One or more OSGi frameworks are run on a server machine. The frameworks interact with one another using remote messaging and mechanisms such as OSGi Remote Services and the Eclipse Communications Framework (ECF), HTTP, web applications, and other conventional server-side technologies.
Solo— One or more OSGi frameworks are run and include HTTP service implementations such as Jetty. As shown in Figure 19-1, server function is exposed as servlets and JSPs and supplied by bundles hooked together by the HTTP service running directly on an OSGi framework. This is the configuration we have been using in Toast.
Bridged— In the Bridged approach, the coding and exposure model is the same as in Solo, but here the OSGi framework is embedded into a web application and run inside a traditional web application server such as Tomcat or WebSphere. This is shown in Figure 19-2.
From my understanding, iDempiere is adopting OSGi by 'Solo' style, embedded Eclipse gemini OSGi web service, am I right?
What I like to do is making iDempiere can be running inside a traditional web application (Bridged type, within Glassfish or Tomcat), it is more mature I believe, but how to make such WAR package?
Thanks & BR,
Ken