@gmail.com
On Wed, Mar 14, 2012 at 13:09,
Marco Rietveld mriet...@redhat.com
wrote:
Hi Alberto,
This is a bug that has been fixed in jBPM. It had to
Sorry, to be clear: a github link to the code you quoted is what I
was after.
03/19/2012 10:33 PM, Marco Rietveld:
Alberto,
Sorry to hear that the bug isn't fixed.
Could you clarify what you mean by these points
Hi Alberto,
This is a bug that has been fixed in jBPM. It had to do with lazy
initialization of a JPAProcessInstanceManager
field.
We'll be releasing a new jBPM version sometime soon (synchronous
with Drools, I think). The bug is fixed in there.
Hi Summeet,
jbpm 3.2.x works with jBoss AS 5.1 -- and obviously also with Drools
5.3, since there's no overlap between those two versions of jbpm and
drools.
I'm not sure if Drools 5.3 works with jBoss AS 5.1, although I think
it does.
There is
look
at jbpm code/internals)
Most of the jbpm core developers monitor both lists.
Thanks,
Marco
11/14/2011 02:00 PM, Marco Rietveld:
Hi Summeet,
jbpm 3.2.x works with jBoss AS 5.1 -- and obviously also with
Drools 5.3
Hi Juan Carlos,
Sorry for the late reply.
Would you mind sending me the Sample.drl en .bpmn files as well?
I happen to have a bit of code that I can use to look into this.
Thanks,
Marco
10/06/2011 01:28 PM, juancarlos.fernandezj:
Hello,
I'm having trouble when trying to insert() facts
Hi Hough,
Unfortunately, there isn't any documentation on this (Container Managed
Persistence w/ jBPM 5) that I know of. I've asked around a little and
couldn't find any.
What are you using transactions for in your case? jBPM itself has some
mechanisms that manage transactions.
Regards,
