Cooee OSGI Support
The Cooee jar file is an OSGI compliant bundle. As such, if working in an OSGI environment, you (almost) don't need to make any changes to get Cooee to work in your relative OSGI environment.
Cooee Activators
Cooee Activator
For Cooee to function correctly in an OSGI environement, it uses an activator so that it can get a reference to its bundle context.
YOU MUST START THE COOEE BUNDLE or it will not detect OSGI, and as a consequence, not see other bundles. As such, if you notice Cooee not finding your resources, Sandbox, etc - this will be your problem.
Cooee Application Activator / Service Registration
While not strictly required to be implemented directly as an activator, any WebContainerServlet implemented as part of a Cooee application that will run under OSGI MUST register itself via the OSGI Http Service.
Cooee and Equinox
Cooee is compatible with both methods of using OSGI on the server side (Web container embedded in OSGI and OSGI embedded in the web container). The Equinox 3.3 package provides all the the required dependencies/plugins to run Cooee within OSGI.
Cooee and S2AP (Spring Application Platform)
At this time (6/05/2008), S2AP does not provide support for the OSGI Http Service. As such, Cooee bundles can not be directly deployed into S2AP without using the PAR file format and removing any or all references to package imports of the OSGI Http Service - including within Cooee itself. For those wishing to use Cooee in a S2AP environment, we recommend the use of the "legacy" WAR file format.
Add Comment