|Home > Guides > Plugin Developers Guide > OSGi Plugin|
This plugin is only experimental and can change in the future.
This plugin provides support for starting an instance of Apache Felix inside a web application, and scanning installed bundles for Struts configuration. An admin bundle is also provided. It can be used with Glassfish 3 as well (Glassfish 3 based on Apache Felix as well), but in such a way
struts.osgi.host must be defined.
There are two ways of organizing bundles. If third party bundles will not be used, then the application bundles can just be placed under
/WEB-INF/classes/bundles. Bundles in this dir will be started in run level 2, the Apache Felix framework's bundles will be loaded in run level 1. If third parties bundles will be used, or you need to start bundles on different run level, create sub dirs under
/WEB-INF/classes/bundles with numeric names (starting from "2" because "1" is reserved for Felix), which correspond to the run level number. For example bundles under
/WEB-INF/classes/bundles/2 will be started in run level 2, and bundles under
/WEB-INF/classes/bundles/3 will be started in run level 3.
Add these lines to MANIFEST.MF:
Now the jar is ready to be deployed. Drop the jar into the
/WEB-INF/classes/bundles directory and it will automatically be installed when the application starts up.
By default Spring OSGi loads its xml config files asynchronously, which causes the OSGi plugin to fail while starting. To fix this add this line to MANIFEST.MF:
Or if using The Apache Felix maven plugin (see below for details):
Please note that you do not need to have the Struts Spring plugin in your application, in order to use Spring with the OSGi plugin.
If you want to use the Spring as the object factory for your actions, then follow these steps:
/META-INF/springin the bundle jar file
/spring(they must be in the classpath, if you are using maven, put thme under /src/resources/spring) in the application
/WEB-INF/classes/bundlesin your application
If you are going to use Velocity results, then add Velocity and Common Digester jars to your application. Using maven:
The Convention plugin will discover actions in bundles in the same way that it discovers them in normal applications. The Convention plugin expects result templates to be (by default) stored under /WEB-INF/content. When packaging actions inside bundles, there won't be a WEB-INF folder, so you must let Convention know where the templates are located. There are two ways of doing so(assuming the templates are under /content):
1. Set the templates location constant in struts.xml (in the application struts.xml, not a bundled struts.xml)
2. Using the ResultPath annotation
The OSGi plugins defines the
osgi interceptor and
defaultStack plus the
osgi interceptor) in the package
osgi-default. This interceptor will check the action and if it implements
org.apache.struts2.osgi.interceptor.BundleContextAware, it will invoke setBundleContext(BundleContext bundleContext) on the action, passing the BundleContext of the OSGi container. The interceptor also checks if the class implements
org.apache.struts2.osgi.interceptor.ServiceAware<T>, if it does, setServices(List<T> services) will be called, where T is the type of a service published in the OSGi container. For example, lets assume an installed bundle publishes a service with the interface
BookPriceLookup, to get all the instances of this service, an action would look like:
Keep in mind that the interceptor is not defined in the default struts package, so when using Convention, you need to specify the parent package as "osgi-default", either using annotations (@ParentPackage), or XML(this XML fragment must be in the struts XML config file in the application, not the bundle's, this is a current limitation of the OSGi plugin):
An admin bundle is distributed with struts, which provides a simple interface to list the installed bundles. Using this interface the bundles can be stopped, started and updated (reloaded from the file system). This interface also provides information on the installed bundles, like OSGi metadata, and a list of packages and actions loaded from each bundle. An interactive AJAX shell is also available, which is just a web interface to the Apache Felix Shell. To use this bundle, just copy the jar file to /bundles (same place where the application bundles are installed) and open http://localhost:PORT/CONTEXT/osgi/admin/ (replace PORT and context)
When a bundle is started, the OSGi plugin will check for the header
Struts2-Enabled in it. If it is set to "true", the bundle will be scanned for XML config and Convention config. When a bundle is stopped, any actions that were loaded from it will be removed from the runtime configuration.
The following settings can be customized. See the developer guide.
The alias of the ObjectFactory to wrap
Any configured alias
The following setting must be set as context parameters in web.xml, because they are used by the StrutsOsgiListener, for example:
If you are running your application on Glassfish 3 (which already contains Apache Felix) you must specify
struts.osgi.host, like below:
Delete all installed bundles when the container starts
true or false
Run level to start the container
Log level for Apache Felix
1 = error, 2 = warning, 3 = information, and 4 = debug
Jar files can be turned into bundles using the Maven Bundle Plugin like: