As it turned out, this problem came about because I had a model that was
based on a POJO jar file. The jar that was in Guvnor contained the
offending field(s), but when the package was being loaded it was using a
version of the jar that did not contain the offending fields. This served
as a lesson to me, demonstrating why updating the serialVersionId is an
important step in managing POJOs.
~ Lance
On Mon, May 6, 2013 at 2:19 AM, Alok [via Drools] <
ml-node+s46999n4023691h60(a)n3.nabble.com> wrote:
Hi Lance,
Even i am facing the issue , what was the work around or what is solution
to fix the issue
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://drools.46999.n3.nabble.com/NoSuchFieldError-session-tp4023263p4023...
To unsubscribe from NoSuchFieldError: session, click
here<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=...
.
NAML<http://drools.46999.n3.nabble.com/template/NamlServlet.jtp?macro=...
--
View this message in context:
http://drools.46999.n3.nabble.com/NoSuchFieldError-session-tp4023263p4023...
Sent from the Drools: User forum mailing list archive at
Nabble.com.