Re: [jbpm-dev] Proposal for jBPM5 first release

Hi Andrea, Export service is much easier than handle the persistence layer. Hibernate is truely hard to integrate into OSGi environment. Since it just store the classname as String and initialize instance everytime. I don't know other JPA framework could handle this. And in the jBPM 4, there is still some classloader issue for running on OSGi environment. Or Maybe we should provide an OSGi platform with jbpm as a system package. So we needn't worry about the classloader issues. regards 2010-05-27 Xu Hui Sheng WebSite: http://www.family168.com/ 发件人： Andrea Zoppello 发送时间： 2010-05-27 16:13:24 收件人： jbpm-dev 抄送： 主题： Re: [jbpm-dev] Proposal for jBPM5 first release 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" and in myprojects i've try to keep it separated, in my typical use case i've used mainly jBPM and i've implemented some custom handler powered by drools to inject in my processes the ability to take different flow according to business rule for which rules are the right solution. 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 2) Be able to use OSGi services within jBPM 3) Be more indepent by persistence layer ( hibernate could be problematic within OSGi.... ) In my current project ( www.spagic3.org ) i've just solved 1) and 2) ant it was not so easy... For the 3) point the only solution i've found quite know it to keep jbp, hibernate and all the dependencies incapsulate in my own bunlde.... and expose through OSGi a my custom API interface.. Andrea Il 26/05/2010 14:17, Kris Verlaenen ha scritto: _______________________________________________ jbpm-dev mailing list jbpm-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbpm-dev