Andrea Zoppello wrote:
Hi Kris,
I'am a jBPM 3 and ( maybe i'm wrong ) i've always considered jBPM as
a "the process engine" and drools as "the rule engine"
Ok, so
that's history and naming, let's just forget about that for a
second ;)
So talking about an OSGi integration, i really means a deep
integration within JBPM. In particular:
1) Be able to expose jBPM API throuhg OSGi services
Yep, definitely a goal.
2) Be able to use OSGi services within jBPM
Ok, not sure we
actually need to add a lot more to be able to do that.
I guess this could be seen as a domain-specific extension maybe, where
the glue code would invoke the OSGi service?
3) Be more indepent by persistence layer ( hibernate could be
problematic within OSGi.... )
The idea is to use JPA, and even that is optional and
pluggable.
Anyway, for now I can only suggest to take a look at how the Drools
project has achieved OSGi integration, as we'll probably use the same
approach. That way you could verify whether that would be sufficient
for you.
Kris