IF this is something you can do, I would suggest to try this: do not
use
your
workaround, but make sure you DISPOSE any existing session(s) before
updating the KB (do not create a new one!) and only then create a new
SESSION to process your next facts.
This is what I was doing all the time before I put my workaround.
I was still getting class cast exception.
--
View this message in context:
http://drools.46999.n3.nabble.com/threw-error-java-lang-ClassCastExceptio...
Sent from the Drools: User forum mailing list archive at
Nabble.com.