Krishna, The dialect configuration affects only semantic code blocks. I.e., consequences, eval() blocks, etc. They are designed to be interchangeable. That is why the examples have rules using each of the dialects. It is mostly a matter of taste, but MVEL is a script language and as so has syntax sugar for nested object access, collections, maps, arrays etc... nothing more than that. Also, MVEL supports java syntax anyway. For instance, assuming you have a class: Person { Map<String, Address> addresses; // gets/sets } The following consequence should run just fine, both in java and MVEL: then $person.getAddresses().get("home").setStreetName("my street"); end Although, MVEL allows you to use a cleaner syntax: then $person.addresses["home"].streetName = "my street"; end It is mostly a matter of taste. []s Edson 2008/5/14 Krishna Satya <krishna.ksatya(a)gmail.com&gt;: -- Edson Tirelli JBoss Drools Core Development Office: +55 11 3529-6000 Mobile: +55 11 9287-5646 JBoss, a division of Red Hat @ www.jboss.com