Did you read the blog, or just look at the examples?
"The final change we hope to do in time for 4.0, which is our most requested feature, is to allow nested properties, array and hashmap access to be expressed as field constraints rather than as predicates, return value or evals."

Stjepan Cvitanovic wrote:

It says on the blog that (quote)
Person($pets:pets)
eval($pets['rover'].type == "dog")
Will soon be able to write as:
Person( pets['rover'].type == "dog" )

Is the same true for nested objects or only for maps?
I can't discern it from the blog post and that would be really helpful....

On 5/19/07, Mark Proctor <mproctor@codehaus.org> wrote:
> By now I would hope you are all subscribed to our
> bloghttp://markproctor.blogspot.com , but for those that aren't I
> thought these two entries would interest many people:
> Making decisions with Rule Flow -
> http://markproctor.blogspot.com/2007/05/making-decisions-with-rule-flow-and.html
> JBoss Rules expressiveness goes to the next level -
> http://markproctor.blogspot.com/2007/05/jboss-rules-expressiveness-goes-to-next.html
>
> Mark
> _______________________________________________
> rules-dev mailing list
> rules-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev
>

--
lp
------
Stjepan
_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev
  