I don't think it's even a matter of choice right now to be honest.
There are still quite a few changes that need to be made before ognl
is suitable for use with T5. (such as the addition of parameter
accessors to handle annotated params, generics, IoC injection ,
removal of static references to ma
No no no...
How can have a null handler now???
If a have a customer -> address -> street in a text component, for example "
custumer.address.street" and i dont instanciate a address, a
NullPointerException is throw. With a ognl null handler, if the address is
null he creates one , like Webwork..
Yep, that's the intention.
Not using OGNL falls into the "blazing speed - no reflection" goal.
Jesse's busy taking the reflection out of OGNL, so it may make a
comeback as an add-on.
On 3/6/07, Davor Hrg <[EMAIL PROTECTED]> wrote:
thnx,
I did add a syntethic property to do the task,
but thought
thnx,
I did add a syntethic property to do the task,
but thought ognl was supposed to work
actualy I like the approach via property more, since then I have
autocomplete and all the stuff I'm used to while writing java code,
and auto reloading of classes makes it as fast to test, as if it was
It may never be; the design of T5 allows for easy property expressions
right in the binding, and more complex expression delegate out to Java
code easily (this is practical in T5 because of the automatic class
reloading).
A lot of the "magic" logic in BeanEditForm and Grid is based on some
APIs t
Hi Howard,
> 2) OGNL isn't supported in T5.
OGNL won't be supported or not yet.
--
Jiří Mareš (mailto:[EMAIL PROTECTED])
ČSAD SVT Praha, s.r.o. (http://www.svt.cz)
Czech Republic
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Fo
Two problems here:
1) Not well formed XML. That "<" inside the test attribute isn't
allow. Use <
2) OGNL isn't supported in T5.
For anything more complicated than a property access, you do the work
in Java code as a synthetic property.
On 3/5/07, Davor Hrg <[EMAIL PROTECTED]> wrote:
Hi,
mayb
