<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rules on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/rules/</link>
    <description>Recent content in Rules on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/rules/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MVEL vs Apache JEXL vs AviatorScript in 2026: Embedded Expression Engines for the JVM</title>
      <link>https://www.pistack.xyz/posts/2026-11-04-mvel-vs-jexl-vs-aviatorscript-jvm-expression-languages/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-04-mvel-vs-jexl-vs-aviatorscript-jvm-expression-languages/</guid>
      <description>&lt;p&gt;The moment a Java application lets a non-developer change behaviour, you inherit an expression language problem. Pricing rules, discount thresholds, alert conditions, feature gates, routing decisions — someone always wants to edit them without a deploy. The first version of that feature is always &lt;code&gt;if (tier.equals(&amp;quot;gold&amp;quot;) &amp;amp;&amp;amp; total &amp;gt; 300)&lt;/code&gt; buried in a service class. The fifth version is a &lt;code&gt;switch&lt;/code&gt; statement nobody dares touch, and the sixth version is an expression engine.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
