Even the full stack trace of the exception would help, to begin with.
I think I see the issue and it should not be too hard to fix, but this
should definitely make it into 5.6
On 04/24/2013 01:16 PM, mohdejaz74 wrote:
I'm still trying to reproduce it ... will post the
View this message in context:
Sent from the Drools: User forum mailing list archive at Nabble.com
rules-users mailing list