MVEL has a pluggable type-conversion API, just like OGNL. Since it's
source-from-many in it's design, you can easily design converters that
perform as much introspection as necessary to determine formatting, etc.
Brian Pontarelli wrote:
Yeah. That's good. The last thing I would toss in as
Taking a brief look at the MVEL type conversion API it could be
somewhat difficult to get this information into the converter on a per
request basis, especially if converters are singleton scoped. This
information isn't available on the source in most cases. It is usually
externalized in
The singleton pattern is used in MVEL, with knowledge of the tradeoff. MVEL
has a strong emphasis on maintaining interpreted-mode performance.
MVEL contains two runtime systems: an interpreter, and a compiler/runtime.
Unlike other ELs, MVEL does not simply bootstrap the compiler, and execute
Here is the documentation for type converters in MVEL:
http://docs.codehaus.org/display/MVEL/Type+Converters
Brian Pontarelli wrote:
Taking a brief look at the MVEL type conversion API it could be
somewhat difficult to get this information into the converter on a per
request basis,
