There is a Link to t5components on the tapestry home page. there you can find
a way to use ognl on t5 while t5.1 is released:
http://87.193.218.134:8080/t5components/t5c-commons/howto_ognlbinding.html
Just download the jars (do not forget the dependencies) and you can use
ognl.
I have used and
I don't either, but i think there are ways to get this working without that
messiness.
My suggestion is for the property resolver to look for static fields. So
that the expression "prop:myComponentProperty.SOME_STATIC_FIELD" could be
resolved, even if myComponentProperty resolves to null.
This wo
Hadn't really planned on it; the last thing I want is for some
OGNL-like messiness with fully qualified class names in the template.
On Thu, Jan 8, 2009 at 9:16 AM, Hugo Palma wrote:
> Is support for accessing class static fields also planned ? That would be
> great.
>
> On Thu, Jan 8, 2009 at 5
Is support for accessing class static fields also planned ? That would be great.
On Thu, Jan 8, 2009 at 5:10 PM, Howard Lewis Ship wrote:
> I've been making improvements to the property expression language for
> 5.1, and there will soon be a boolean not operator.
>
> Already you can now invoke me
I've been making improvements to the property expression language for
5.1, and there will soon be a boolean not operator.
Already you can now invoke methods with parameters, and the
upper/lower bounds on range expressions are themselves expressions.
(i.e, you can now say "from .. to" where from an
Ah, and you could also do it like this:
public boolean isNextPageLinkDisabled{
return ! sth;
}
Andy
Brian Long schrieb:
Hi,
in tapestry 4 you could use ognl to check a page property in a
expression like disabled="ognl:!nextAvailable" or ognl:(nextAvailable
== false)", I'm wonderin
Hi,
this is definetly not possible with T 5.0.x.
I think Howard already checked in some changes in T 5.1 that make it
possible.
As a workaround you could use ognl as in T4. See
http://www.chenillekit.org/chenillekit-tapestry/ognlbinding.html
Andy
Brian Long schrieb:
Hi,
in tapestr
Hi,
in tapestry 4 you could use ognl to check a page property in a
expression like disabled="ognl:!nextAvailable" or ognl:(nextAvailable ==
false)", I'm wondering is we can do something similar in T5 without
using ognl, just using the prop: binding prefix alone, for example
public final b
