Michael, I think the class is just incidentally named ValidationError.

The problem is in the "wiring" of the accessors into the FieldDefinition
(you see that "accessor=null" at the end of the toString in the failing case).
This wiring is done by the PackageBuilder when the DRL is compiled, so
I suspect that there is a problem with the interaction of the data modeller
and the package builder..

Jarkko, thanks for reporting this, it really looks like a WB bug!
Could you please open a JIRA ticket?

Davide

On 03/15/2014 04:09 PM, Michael Anstis wrote:

ValidationError is indeed an *internal* workbench class. What makes you think you can query for it?

Sent on the move

On 15 Mar 2014 12:00, "JarkkoMakela" <jarkko.matinpoika@gmail.com> wrote:

This ValidationError is created with drools workbench data modeller. It has
only String fields.
I have only couple of rules (which will create two ValidationErrors) and one
query (for the ValidationError) in the knowledgebase.


-Jarkko



--
View this message in context: http://drools.46999.n3.nabble.com/NullPointerException-with-factType-get-fact-fieldname-tp4028688p4028744.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users