IF this is something you can do, I would suggest to try this: do not
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:
Sent from the Drools: User forum mailing list archive at Nabble.com