In Tapestry 4, OGNL had to do a lot of heavy lifting, since you didn't have
reloadable Java classes; thus I've seen lots of very complicated OGNL
expressions mixed into T4 templates. That causes its own problems in terms
of maintainability and brittleness in the face of refactoring.
Simply compar
Yeah, I keep forgetting about the non-null binding to a boolean true
(see Notes section in the IF component docs) - a really cool idea!
--
Steve Eynon
On 5 August 2010 18:33, based2 wrote:
>
> http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/If.ht
http://old.nabble.com/T5%3A-using-an-expression-in-t%3Aif-ts21931606.html#a21931606
http://old.nabble.com/T5%3A-Using-expression-language-in-If-component-ts16561976.html#a16561976
Angelo Chen wrote:
>
> Hi,
> is it possible to use an expression in the t:if? something like this
>
> < t:if test=
http://tapestry.apache.org/tapestry5.1/tapestry-core/ref/org/apache/tapestry5/corelib/components/If.html
Angelo Chen wrote:
>
> Hi,
> is it possible to use an expression in the t:if? something like this
>
> < t:if test="user.id=99">
> < /t:if>
>
> ?
>
--
View this message in context:
http
Nope, you can't... T4 used OGNL where you could, but T5 is pretty much
just calls bean properties. See here:
http://tapestry.apache.org/tapestry5.2-dev/guide/propexp.html
But this is a good thing, for it stops you from putting logic and
programming in your template.
So what you can do is:
< t:i
Hi,
is it possible to use an expression in the t:if? something like this
< t:if test="user.id=99">
< /t:if>
?
--
View this message in context:
http://old.nabble.com/t5%3A-if-and-expression-tp29355495p29355495.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
