This is actually pretty close to what Guvnor does if you click "Validate" in the editors. The reason is that we don't want to compile a full rule base for each click of validate. You can reuse the codes we use for validation. ^ That is how Guvnor 5.x and older Guvnor's work. In Drools workbench 6.0 (=Guvnor 6.0) the validate feature will most likely use incremental builds. Toni On Jun 10, 2013, at 1:41 PM, rjr201 wrote: > I'm creating a system which embeds the Guvnor Guided Editor and uses the REST > API to allow the user to edit and create rules. > > I can't trust the user to create syntactically correct rules. If they do > create an invalid rule then the whole package of rules will fail to compile. > I need to find a way to detect that a individual rule has broken, and point > the user to that rule. So they don't just sit there not understanding why > it's not working. > > I can see that when using standalone Guvnor this wouldn't be a problem, as > the user would be able to see that the rule has a red cross next to it > meaning something is wrong with that rule. > > Has anyone else had experience doing this? Is there a way to get the UUID of > the specific rule that is causing the package not to compile? > > > As always, thanks any help/advice anyone can give. > > > > -- > View this message in context: http://drools.46999.n3.nabble.com/Guvnor-Rule-Validation-tp4024218.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users