I would say the reason you don't want to dive into 233 would be
primarily because of performance. You'd either need to have a compiled
statement cache or pre-compile. Most of the scripting frameworks that
comply with 233 are full blow languages (Groovy, JavaScript, etc) and
have pretty
I sorta figured it would be pretty slow. You might also run into some
issues with the APIs depending on how you want to handle type
conversion stuff.
The JCatapult EL is mostly decoupled from the rest of the framework
except that I use the JCatapult ObjectFactory to create instances of
yes, type conversion has been a pain for me, and the reason why I
couldn't just use MVEL. Implementing value look ups is easy with any
of the ELs, setting values is a different matter, because other ELs
don't have an API as flexible as OGNL.
If you are not using bytecode for getting/seeting
Yeah, same here. Everything broke down when it came to two use cases:
- The difference between a user type conversion error (user puts in
'a' in a text box that is mapped to an Integer field property) and a
developer type conversion error (developer didn't specify the date
format for a