<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
MVEL compiles the string to it's own evaluation tree, it then
"evaluates" that tree at runtime so simulate runtime code. We do a
further optimisation for performance where after MVEL executes a
statement so many times, we'll JIT it to bytecode to get improved
execution performance.<br>
<br>
Mark<br>
On 26/03/2012 20:04, Mike Melton wrote:
<blockquote
cite="mid:CAAZ+K3-xrLnXP0-+g=ek_j5E82JMtvv4n9-gux_5fOYN4MCX=g@mail.gmail.com"
type="cite">My team is using Drools on a government project. As is
usually the case with government projects, the security folks have
their hands in every aspect of the project. They have big
questions on MVEL, but I'm going to try to boil them down to one
simple question:<br>
<br>
At what stage(s) of Drools's lifecycle does MVEL interpretation
occur? I think that the compilation engine interprets the MVEL at
compile time and converts it to generated Java code, though I
don't know enough about the internals of the engine to say for
sure. Stated another way, does Drools interpret rules written
using the MVEL dialect at runtime?
<div>
<br>
</div>
<div>Thanks</div>
<div>Mike</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
rules-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-users@lists.jboss.org">rules-users@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-users">https://lists.jboss.org/mailman/listinfo/rules-users</a>
</pre>
</blockquote>
<br>
</body>
</html>