01-21-2011 03:40 PM
01-31-2011 01:13 PM
01-31-2011 03:12 PM
02-03-2011 03:17 AM
02-03-2011 06:11 AM
I don't have cleaned up the code yet but will do this as soon as possible and upload it to my github repo too.Great, please send info when it's ready
What I have done basically here is that I am using the blueprint approach for Activiti itself to get it started, although I also extended the available JTA Engine Configuration to be able to reference a datasource provided by the container using its JNDI name.Yes, this is basically what I'm also doing - using gnodet work on OSGi-fying Activiti - however I would prefer using OSGi services to expose datasource.
I also do not use the Aries version from servicemix in favor the official one, directly inside our GlassFish 3.1 (b36 currently) and I use the OSGi/JTA integration to reference the transaction manager.Do you mean reference implementation by 'official one'? Aries implementation is quite complete - http://aries.apache.org/downloads/ct/current-release/org.osgi.test.cases.blueprint.html, the only extension I used
The OSGi Service ELResolver I have written basically works with ServiceTracker to get a service instance. Also it is packaged in a separate Fragment bundle (attaching to activiti-engine) to be able to specify custom OSGi imports that will be required when integrating that into an application while preserving the OSGi setup of all other Activiti bundles.Did you consider using BlueprintContainer? It's part of standard, and I find it easier to use than service tracking - or do you need some other functionality?
P.S.: I see that you're from TouK, are you considering Activiti as a "replacement" for ODE? I've worked quite hard on a nice and advanced OSGi setup of ODE into JavaEE servers (GlassFish 3.1 preliminary).Well… we found using BPEL extensively quite a pain One of the main reasons we did that is because it's standard… So now when we have BPMN 2.0 we hope to use Activiti in new projects I remeber that somebody contributed more advanced ODE OSGi setup than I did initially - was that you?
02-03-2011 09:42 PM
Hi,
I see we came up to quite similar approach independentlyI don't have cleaned up the code yet but will do this as soon as possible and upload it to my github repo too.Great, please send info when it's readyWhat I have done basically here is that I am using the blueprint approach for Activiti itself to get it started, although I also extended the available JTA Engine Configuration to be able to reference a datasource provided by the container using its JNDI name.Yes, this is basically what I'm also doing - using gnodet work on OSGi-fying Activiti - however I would prefer using OSGi services to expose datasource.
I also do not use the Aries version from servicemix in favor the official one, directly inside our GlassFish 3.1 (b36 currently) and I use the OSGi/JTA integration to reference the transaction manager.Do you mean reference implementation by 'official one'? Aries implementation is quite complete - http://aries.apache.org/downloads/ct/current-release/org.osgi.test.cases.blueprint.html, the only extension I used
is ability to load properties easily - but guess blueprint implementation doesn't really matter that much…
The OSGi Service ELResolver I have written basically works with ServiceTracker to get a service instance. Also it is packaged in a separate Fragment bundle (attaching to activiti-engine) to be able to specify custom OSGi imports that will be required when integrating that into an application while preserving the OSGi setup of all other Activiti bundles.Did you consider using BlueprintContainer? It's part of standard, and I find it easier to use than service tracking - or do you need some other functionality?
I ended up using DynamicPackage-Import - as I probably want to use pretty random packages as serviceTask implementations
P.S.: I see that you're from TouK, are you considering Activiti as a "replacement" for ODE? I've worked quite hard on a nice and advanced OSGi setup of ODE into JavaEE servers (GlassFish 3.1 preliminary).Well… we found using BPEL extensively quite a pain One of the main reasons we did that is because it's standard… So now when we have BPMN 2.0 we hope to use Activiti in new projects I remeber that somebody contributed more advanced ODE OSGi setup than I did initially - was that you?
cheers,
maciek
02-06-2011 10:16 AM
02-08-2011 03:02 AM
05-25-2011 11:33 AM
05-25-2011 03:56 PM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.