hi,
thanks for that solution!
i will try to find a reason of this strange behaviour debugging
tapestry's sources. in worst case i will give up using your workaround.
best regards,
m.
Moritz Gmelin wrote on 02 Jun 2009 20:52:58 MET:
> Hi,
>
> I had a very similar problem today too. Sometimes the body was
> rendered, other times just nothing was rendered.
>
> My workaround was to define a block containing the body part, pass
> this block to the "report" and have it rendered through <t:Deleget
> to="passedBlock" />
>
> your report.tml would look like
>
> > <t:loop source="items" value="row">
> > <tr>
> > <td> test </td>
> > <t:delegate to="passedBlock" />
> > </tr>
> > </t:loop>
>
> the page would be
>
> > <t:report t:id="users" model="reportModel" row="userObject"
> > passedBlock="innerBlock"/>
> <t:block t:id="innerBlock">
> > <td> blah blah </td>
> > <td> ${userObject.username} </td>
> > </t:block>
>
> you'd have to define passedBlock in report.java and innerblock in
> page.java
>
> like
>
> @Inject
> @Property
> private Block passedBlock;
>
> Hope this helps.
> Problems like this make me nervous. I hope someone could explain why
> it is not working as expected.
>
> Regards
>
> Moritz
>
> Am 02.06.2009 um 20:19 schrieb grabarz:
>
> > hi,
> > this is one of these 'mysterious' problems. i have a component
> > (report)
> > which takes a datasource and draws a table filled with data. something
> > like a grid component provided by tapestry.
> >
[cut]
--
Mess with the best, die like a rest!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
