iberck wrote:
Hi, I'm developing an application with tap 5..
Great, good new. Welcome on board !
I don't understand why I can't use OGNL inside tap5 and with tap4 yes !
That's a design choice made by HLS. OGNL suffer some drawbacks,
including a performance penalty (even after the
For additional commands, e-mail: users-h...@tapestry.apache.org
--
View this message in context:
http://www.nabble.com/-T5--Expression-Language-tp21674223p21685501.html
Sent from the Tapestry - User mailing list archive at Nabble.com
iberck wrote:
thank you of your response and your time
Now I understand the concept.
No problem :)
--
Francois Armand
Etudes Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
---
http://fanf42.blogspot.com
InterLDAP - http://interldap.org
, what is the alternative?
--
View this message in context:
http://www.nabble.com/-T5--Expression-Language-tp21674223p21674223.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
I think for T5 as default:
Tapestry's binding language might be extended to do some simple
evaluation at best, and nothing more! the simpler the better in my
view, isn't this the general idea of using components and moving away
from embedded scripting? I think, in general, support for
There's been a lot of interest in and expanded version of the T5
expression language. I know T4 was equipped with ognl and people seem to
have liked that very much. I could very well be off base here, and there
may be a good reason for having chosen ognl before - but I'm curious -
if what
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
(and this is statically, when bindings are prepared)
I think I saw that ognl has methods that calculate
return
of course, youll need the dependancy in your pom:
dependency
groupIdognl/groupId
artifactIdognl/artifactId
version2.6.9/version
/dependency
On Nov 16, 2007 8:42 PM, Davor Hrg [EMAIL PROTECTED] wrote:
ognl can be easily added as a binding prefix,
however expect
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
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
Oh wellit wouldn't hurt my feelings if anyone used MVEL. I'm
only as loyal to the best technology and hope everyone else would be
too.
On Nov 16, 2007 4:35 PM, Davor Hrg [EMAIL PROTECTED] wrote:
thanks,
I've played with it only a bit...
It was that time that MVEL was said to be much
11 matches
Mail list logo
