I finally found the root cause. The reason was incompatibility between model
classes uploaded to guvnor and classes referenced by client application (The
model classes in client app implement additionally Serializable interface
required by JPAKnowledgeSession).
So the root cause was slightly different than what I found in logs.
I'm wondering if this is possible to make the error more accurate in such
situation. Is it drools or java who throws this exception?
/danielje
--
View this message in context:
http://drools.46999.n3.nabble.com/java-lang-IncompatibleClassChangeError-...
Sent from the Drools: User forum mailing list archive at
Nabble.com.