Hi Ove,

While I would really like to be able to say "we'll do that!" with regards to JPA2 compliant artifacts, the reality is that I don't think this will happen any time soon -- my apologies for this.

This is mostly due to the complex release cycle/procedure that jBPM shares with Drools -- and the amount of work to be done in general.

That's not to say it will never happen: what I might try to do with the next major release, is release jpa2 artifacts myself -- if the rest of the team doesn't have a problem with that.

@Kris: jpa2 compliant artifacts with the next release?

This would mean taking the tag used for the release (5.4.0.Final?) and then doing a release/deploy using the hibernate-4 profile (hibernate 4 dependencies, JPA 2 xml configuration files.. ). Of course, this would mean that all tests would have to succeed on that profile first.

In short, Ove, I'll definitely keep it in mind, but I can't promise anything. :)

(Sorry for the late reply, btw! )

Marco

04-07-12 17:29, Ove Ranheim:

Hi Marco, Sorry for my late reply, but today I had time to verify the hibernate-4 support in Drools 5.4 and jBPM 5.3. It works just fine! I don't use the human task, so I haven't checked that out yet. In fact I only had to add the 'entity'-descriptor to my JBPMorm.xml in my app. and it successfully deployed. I'm glad my initial pull request was of help after all. Thanks a lot for doing this! Btw, it would be nice if jpa2 compliant artifacts where released in nexus on regularly basis. Cheers, Ove On Jun 28, 2012, at 9:56 AM, Marco Rietveld wrote:

Hi Ove! I did some work on this early this year -- thanks very much for your pull request, it made my work a lot easier. We've done the following in the past year: - changed jbpm-persistence-jpa so that the hibernate 3.3 dependency is no longer hard-coded into the code, so to speak - I know that Mauricio corrected some queries in human-task that weren't JPA 2 compliant. - added a "hibernate-4" maven profile that you can compile using hibernate 4/JPA 2. I might have done one or two other things for this, but I can't remember them any more -- which means they also weren't of any consequence. Regardless, see http://mriet.wordpress.com/2012/04/03/jpa-2-with-drools-and-jbpm/ Ignore the second part (¨Developer bits and ranting"), I just reread it and had trouble following it myself.. :/ When I initially did all of this work, there were 2 or 3 problems in various modules -- code that worked under hib 3.3/jpa 1 but not hib 4/jpa 2. Unfortunately, while one or two might have been fixed (human-task queries), I think that there are probably one or two still left -- these were problems that I was at a loss to explain/fix at the time. Thanks, Marco 22-06-12 19:27, Ove Ranheim:

Hi guys, Earlier this year I provided a patch for Drools and jBPM to support Hibernate 4 and JPA2. My git commit was rejected due to committed to EAP5. Reasonable enough. Now that EAP6 is key to JBoss. What plans do you have in Drools and jBPM to support Hibernate 4 and JPA2? I'm still running on my patched version of Drools and jBPM in such respect and look forward to be able to comply with future stack releases. Cheers, Ove www.musific.com _______________________________________________ jbpm-users mailing list jbpm-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbpm-users