Hi, On Wed, Apr 27, 2011 at 5:03 PM, Alessandro Adamou <[email protected]> wrote: > ...there seem to be some early adopters who are interested in using Stanbol, > yet would like to run it in non-OSGi environments....
I see two (almost) out-of-the box ways: 1) Run the stanbol jar in a separate JVM and access it via its http interfaces 2) Create a war file that embeds the OSGi framework and Stanbol bundles, and run in a J2EE server alongside other code The maven-launchpad-plugin supports 2) but it's not currently configured in our launcher's poms, should be fairly easy to add. See http://sling.apache.org/site/maven-launchpad-plugin.html Next option is http://code.google.com/p/pojosr/ which I haven't tested yet but might help. IMO, supporting non-OSGi environments outside of 1) and 2) is out of scope for Stanbol, that would distract us from our primary goal. You'd need to provide lifecycle, service registry, ConfigurationAdmin and a number of other things that probably forget, that's a lot of work that doesn't help fulfilling our own goals. -Bertrand
