People, Just as an explanation, the DRL language is a fairly complex language from a parser perspective. We generate our parser using ANTLR that is an amazing tool, but due to the complexity of the grammar, it is hard to foresee all possible runtime exceptions that might occur when someone uses an incorrect syntax. In such cases, the parser may raise a runtime exception like a NPE. To avoid blowing the application using the parser or the Drools IDE, we added a catch all exceptions with the message: "this is a bug, contact the development team" when that happens. This is to direct you, users, to report us what kinds of incorrect syntax make the parser explode. Once found, it is farly easy to fix. So, thanks for reporting. I opened a JIRA for that. If anyone knows of other cases that cause the same kind of errors, please add comments to the ticket. Also, if someone would like to contribute to the project by getting some trained zoo monkeys to bash the keyboard looking for invalid sentences that blow up the parser, it is highly appreciated. ;) https://jira.jboss.org/jira/browse/JBRULES-2151 Cheers, Edson 2009/6/30 Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; -- Edson Tirelli JBoss Drools Core Development JBoss by Red Hat @ www.jboss.com

The second operand of a constraint is either a literal, a variable or a *parenthesized *expression. Try ... ( serializationIdentifier == *(* generateSN(...)* )* ) from ... On 28 October 2010 10:49, pjeynes <paul.jeynes(a)almacgroup.com&gt; wrote:

But the IDE did tell you to contact the team - so thanks for that. This will help improve the parser/compiler. On Fri, Oct 29, 2010 at 2:36 AM, pjeynes <paul.jeynes(a)almacgroup.com&gt; wrote: -- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com