<br>&nbsp;&nbsp; Godmar,<br><br>&nbsp;&nbsp; I copied and pasted your rule and run a simple test using the same version of jars you mentioned bellow, but I can&#39;t reproduce the problem you are having. If it is still a problem for you, can you zip a sample test showing the problem and send us?<br>
<br>&nbsp;&nbsp; Thanks,<br>&nbsp;&nbsp;&nbsp;&nbsp; Edson<br><br><div><span class="gmail_quote">2008/2/13, Godmar Back &lt;<a href="mailto:godmar@gmail.com">godmar@gmail.com</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I&#39;ve recently upgraded to Drools 4.0.4 with mvel14-1.2.21.jar, and I&#39;m<br>having severe issues with its parser.<br>For instance, this simple .drl file:<br><br>--<br>package test;<br><br>rule &quot;Rule #1&quot;<br>
dialect &quot;mvel&quot;<br>when<br>then<br>&nbsp;&nbsp;&nbsp;&nbsp;/* a single-line comment */<br>&nbsp;&nbsp;&nbsp;&nbsp;System.out.println(&quot;hello world&quot;);<br>end<br>--<br><br>results in:<br>org.mvel.PropertyAccessException: unable to resolve property: ;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:285)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:107)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.ASTNode.getReducedValueAccelerated(ASTNode.java:185)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.MVELRuntime.execute(MVELRuntime.java:88)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.CompiledExpression.getValue(CompiledExpression.java:107)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.mvel.MVEL.executeExpression(MVEL.java:223)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:47)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:550)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:514)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:471)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:433)<br><br>--<br>Switching to dialect &quot;java,&quot; or removing the /* single-line comment<br>
*/, helps. So does replacing the comment with a // style comment.<br>There are many more weirdnesses I&#39;m encountering (I&#39;ve filed a number<br>of bugs already), but I&#39;m wondering if something else isn&#39;t amiss<br>
here.&nbsp;&nbsp;I also tried mvel16-1.2.22.jar, same effect. On the other hand,<br>running just the RHS in mvelsh works just fine.<br><br>In this context, I&#39;d like to voice the wish that Drools include a<br>command-line driver that can load and execute .drl files for testing.<br>
<br> - Godmar<br>_______________________________________________<br>rules-users mailing list<br><a href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>&nbsp;&nbsp;Edson Tirelli<br>&nbsp;&nbsp;JBoss Drools Core Development<br>&nbsp;&nbsp;Office: +55 11 3529-6000<br>&nbsp;&nbsp;Mobile: +55 11 9287-5646<br>&nbsp;&nbsp;JBoss, a division of Red Hat @ <a href="http://www.jboss.com">www.jboss.com</a>