[rules-users] Drools Pattern to Eat Real Exceptions

I am just curious to learn a little more about Drools evolution history to understand why would Drools eat so many Exceptions the root cause of which is impossible to even guess, without stepping into the Drools source code... That happens in many Drools components, so my curiosity just wanted to be fed on how this "pattern" came to be. Any old school Droolers can contemplate? /Anatoly -- View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Pattern-to-Eat... Sent from the Drools - User mailing list archive at Nabble.com.