[
https://issues.apache.org/jira/browse/SHINDIG-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777953#action_12777953
]
Mikhail Kotelnikov commented on SHINDIG-1225:
---------------------------------------------
Some times ago we tried to use Shindig under OSGi...
We could not find a clean solution. Our workaround was:
* Package all Shindig jar files in one bundle. All jars were in the "/lib"
folder of this bundle
* This bundle imported some packages defined in separate bundles: like
javax.servlet, org.apache.commons.logging, log4j and so on
* The activator of this bundle explicitly listens the HttpService OSGi service
and creates, configures and registers all Shindig-specific servlets. To avoid
the problem described here http://markmail.org/thread/fqechw5ek7uxnehw we use
a fake configuration servlet used to create a Guice injector and register it in
a HttpContext common for all Shindig servlets.
You can find our OSGi activator class in the attachment below.
> Make Shindig jars available as OSGi bundles
> -------------------------------------------
>
> Key: SHINDIG-1225
> URL: https://issues.apache.org/jira/browse/SHINDIG-1225
> Project: Shindig
> Issue Type: Improvement
> Components: Java
> Reporter: David Johnson
>
> Make changes to the Shindig-Java build process so that the Shindig Jars are
> each available as OSGi bundles.
> See also:
> November 2009 thread: Shindig and OSGi
> http://markmail.org/thread/hrozofu6mkyj3bm4
> May 2009 thread: Shindig as an OSGi Bundle
> http://markmail.org/thread/fqechw5ek7uxnehw
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
