<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">5.x supports free form expressions. This means it is not a trivial thing to analyse.<div><br></div><div>In a pattern there will be 1..n strings for each expression. You'll need to build that string with MVEL and then analyse the MVEL AST tree.</div><div><br></div><div>Take a look at drools-compiler PatternBuilder and <font face="Monaco"><span style="font-size: 11px;">MVELExprAnalyzer. These don't show how to extract fields, but it does show you how we analyse patterns for other mvel content.</span></font></div><div><br></div><div>Mark<br><div><br></div><div><br><div><div>On 18 Jan 2013, at 15:47, jeetendray <<a href="mailto:jeetcyb@gmail.com">jeetcyb@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Thanks Mark.<br><br>can you also please tell me the alternative to ORConstraints,<br>LiteralConstraints. I read about fetching field inside condition that drools<br>5.x has better way to do it, without worrying about getting into internal<br>classes.<br><br>Any help will be highly appreciated. <br><br>Regards,<br>Jeetendra.<br><br><br><br>--<br>View this message in context: <a href="http://drools.46999.n3.nabble.com/Drools-5-5-API-doc-doesn-t-show-all-classes-tp4021634p4021650.html">http://drools.46999.n3.nabble.com/Drools-5-5-API-doc-doesn-t-show-all-classes-tp4021634p4021650.html</a><br>Sent from the Drools: User forum mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-users<br></blockquote></div><br></div></div></body></html>