It's created in the normal way. X x_obj = new X(); kSession.insert(x_obj); I am using drools 6.0.1.Final. I do not get a stack trace from Eclipse. But the null pointer exception is displayed on screen when I click on the Rete Tree tab. -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

I can't give you my exact code as it is company-sensitive code. But you can test this against any POJO with a few int and Integer fields. I'm trying to promote Drools Expert in my organisation so I would appreciate your help. It's not causing a problem with rule evaluation. That is working fine. But it doesn't look good when things which should be working are not. -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

@laune, were you able to reproduce this? -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

@laune, it is the same problem in version 6.0.0.Final. please try with that version if you have it already. Thanks -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

Please open a JIRA ticket, this is the way bugs are reported to the development team. https://issues.jboss.org/browse/DROOLS Davide On 02/20/2014 03:38 PM, droolster wrote:

@Mark, "We saw this message..." - then why wasn't the advice given to raise a bug earlier? Why did it take 8 posts to eventually get to that point? It's a waste of time and effort, and a lack of appreciation for people who are trying to promote your product in their industry and workplace. Your other point about the Rete Viewer being low priority. For developers who are new to Drools (like me), one of the assurances we get that our rules are properly defined is the Rete viewer. If the Rete Viewer shows errors, then it gives doubts about whether the rules are properly defined. In my case, the rules still function correctly but if I am going take my rule engine into a Production environment I want all the assurances I can get. Thank you for eventually replying to my post. -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

@laune, I don't want to make this thread longer than it already is but... 1. If you don't trust the Drools Rete Viewer, why is it there in the plugin and why are Rete graphs displayed in the documentation? If it is not trustworthy, then it's misleading. (I'm assuming you are on the Drools dev. team). 2. I said in my post "one of the assurances...". We do have JUnit tests in place. But it was source of confusion that the Rete viewer was complaining that the graph was broken (in the properties tab, there was null for one of nodes) but the rule's were evaluating fine. It's not exactly a glowing advert for Drools Expert is it? -- View this message in context: http://drools.46999.n3.nabble.com/in-operator-breaking-the-Rete-Tree-tp40... Sent from the Drools: User forum mailing list archive at Nabble.com.

No, this forum is very active, and I'm sure your mails have been noticed. But the display of the Rete tree has very low priority, and I guess that the core development team waits for someone to pick this up and fix it. I haven't set up Eclipse for anything newer that 5.5 yet. -W On 20/02/2014, droolster <quant.coder(a)gmail.com&gt; wrote: