What Tapestry is doing now in 5.1 is correct. In you example, the
<div> will *always* render empty, and only if user is null in 5.0. 5.1
forces you to put the <p:else> where it makes sense. The Tapestry 5.0
documentation should have been more specific, that you place it
*directly* inside the body of the component (not merely somehwhere
inside).
On Thu, Jun 4, 2009 at 6:29 AM, Geoffrey Wiseman
<geoffrey.wise...@gmail.com> wrote:
> On Thu, Jun 4, 2009 at 4:04 AM, Stefan Esterer <der.ste...@gmail.com> wrote:
>
>> This works perfectly fine. Only if I add a additional <div> I get a
>> problem.
>>
>> <t:if test="user">
>> Welcome back, ${user.firstName}
>> <div>
>> <p:else>
>> <t:pagelink name="login">Login</t:pagelink> /
>> <t:pagelink name="register">Register</t:pagelink>
>> </p:else>
>> </div>
>> </t:if>
>>
>
>
> Why would you do that, just for previewability? That structure doesn't make
> a ton of sense to me. If there's a user, should tapestry render:
>
>> Welcome back, Stefan Esterer<div></div>
>>
>
> And if there's no user:
>
>> <a href="login">Login</a> / <a href="register">Register</a>
>>
>
> I'm curious for the people who are getting bitten by this what they have in
> mind.
>
> - Geoffrey
> --
> Geoffrey Wiseman
> http://www.geoffreywiseman.ca/
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
Director of Open Source Technology at Formos
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
