Thanks everyone for the help :)Its working fine with jbpm 5.3
development snapshot and drools 5.4 cr1... cheers!!
On Mon, Apr 16, 2012 at 3:08 PM, sumatheja sumath...@gmail.com wrote:
Thanks Edson... I expected this could be a ersion issue... can you send me
the link for the latest
This kind of error indicates some confusion between compilation and
execution of the code where this is thrown.
Also, which versions of Drools do you used for marshalling and
unmarshalling? There's no line 287 in the versions of
org.drools.marshalling.impl.PersisterHelper.java available to me.
Hi,
I'm using drools and guvnor 5.4 cr1. I've few drools ruleflows which
were not executing so I imported the jars from jbpm 5.2 final. The
marshalling and unmarshalling works fine if I have knowledge base without
rule-flows. I hope this gives some hint..
On Mon, Apr 16, 2012 at 11:29
I'm getting the same issue when I try to unmarshall a sample application
which has the jbpm process (which moves out guvnor as possible cause).
can someone guide if this is some bug? or should I change the jbpm jar
version?
On Mon, Apr 16, 2012 at 11:37 AM, sumatheja sumath...@gmail.com
There was a dramatic change to the marshalling of binary packages for
5.4.CR1. AFAIK this would mean any existing binary package in Guvnor would
need to be rebuilt.
Downgrading JARs to older versions would effectively remove the marshalling
change and hence restore compatibility of older binary
Hi Michael... Thanks for the response I'm getting this exception even
without a guvnor i.e. when I use a local project which has jbpm process and
a drl file but without the jbpm process everything works fine. I'm
using jbpm 5.2 final.
2012/4/16 Michael Anstis michael.ans...@gmail.com
The error means a version incompatibility due to changes we made to the
marshalling framework. Until both projects have their releases out, you
will have to use snapshots. jBPM 5.3 requires Drools 5.4 and vice-versa.
You can't use Drools 5.4 with jBPM 5.2.
I think jBPM 5.3 has not released
Thanks Edson... I expected this could be a ersion issue... can you send me
the link for the latest snapshot for jBPM... The latest that I could find
is 5.2 final.
2012/4/16 Edson Tirelli ed.tire...@gmail.com
The error means a version incompatibility due to changes we made to the
