I haven't seen any obstacles to a change like that. It would be nice if we
could reuse a param binding implementation with type-conversion from
somewhere else rather reinvent another.
Yes, definitely. Any suggestions? What is the status of Commons beanutils?
musachy
--
Hey you! Would you
Should we continue to use OGNL for parameter binding? This creates so
many possible security holes, in exchange for pretty much nothing,
when parameter names should be simple (indexing + the old A.B.C
notation).
Are there any uses cases where the full OGNL power is needed, for
parameter binding?
I wrote my own for the JCatapult MVC and it does most of the parameter
setting stuff that OGNL does and a few other things like handling
generics correctly and completely. It also has a pretty solid type
conversion API. Took about 3 days to write, test and complete. Feel
free to grab the
