Details
Description
Some things might cause problems in an OSGi environment like
- classloading
- dependencies from the api to the impl (@see
ACT-8)
First task is to create a valid OSGi bundle out of the Activiti jar file. I believe this would include specification of the API packages. And maybe some lifecycle methods that could delegate to ProcessEngines.init and ProcessEngines.destroy.
What interface/object would be published? A single ProcessEngine object?
I would like this to be done as a separate module called activiti-osgi. The work should be presented on a branch called https://svn.codehaus.org/activiti/activiti/branches/osgi The goal is to show in a unit test that osgi-activiti-usage bundle would be able to access the services offered from the activiti-osgi bundle.
Issue Links
- is related to
-
ACT-360
Provide an osgi web bundle for the rest api
-
- relates to
-
ACT-228
The Activiti engine can not be used in OSGi due to classloading problems
-
-
ACT-227
Allow ProcessEngineFactoryBean to be reused outside of a spring context
-
-
ACT-222
Make activiti jars valid OSGi bundles
-
-
ACT-235
Add an OSGi extender to deploy activiti processes as osgi bundles along with the needed URL handlers and fileinstall deployers
-
-
ACT-8
Circular dependencies from top-level package to subpackages
-
I'll work on that. I've already raised
ACT-222to make activiti-pvm and activiti-engine valid OSGi bundles.