5.x supports free form expressions. This means it is not a trivial thing to analyse.
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.
Take a look at drools-compiler PatternBuilder and MVELExprAnalyzer. These don't show
how to extract fields, but it does show you how we analyse patterns for other mvel
content.
Mark
On 18 Jan 2013, at 15:47, jeetendray <jeetcyb(a)gmail.com> wrote:
Thanks Mark.
can you also please tell me the alternative to ORConstraints,
LiteralConstraints. I read about fetching field inside condition that drools
5.x has better way to do it, without worrying about getting into internal
classes.
Any help will be highly appreciated.
Regards,
Jeetendra.
--
View this message in context:
http://drools.46999.n3.nabble.com/Drools-5-5-API-doc-doesn-t-show-all-cla...
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