thanks, I've played with it only a bit... It was that time that MVEL was said to be much faster than OGNL and very long flame on serverside.
I've just wanted try both, and made a small project that adds both binding prefixes.. (I was not testing speeds .. just integration...) after playing with it I was more satisfied with OGNL, and MVEL crashed on some simple examples when byte code optimizer was turned on for it. Davor Hrg On Nov 16, 2007 10:06 PM, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > You can know the type in advance by calling > OgnlContext.getCurrentType() after evaluating an expression (or > getPreviousType() / getFirstType() / the type and accessor types are > all pushed on to a stack now).. > > It also supports generics / enums / varargs / etc now.. > > On Nov 16, 2007 2:42 PM, Davor Hrg <[EMAIL PROTECTED]> wrote: > > ognl can be easily added as a binding prefix, > > however expect some features to not work > > because tapestry in some occasions needs to > > know in advance type that the expression will return > > > <snipped> > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
