I agree, Chris. _resources.findBlock has got to be where the trouble is.
Somehow the rendering order on Layout winds up only looking at the last
rendering of the block.
Bill
On Fri, May 2, 2008 at 2:19 AM, Chris Lewis <[EMAIL PROTECTED]>
wrote:
> Hi Bill,
>
> You normally have some interesting questions :-) - I don't see
> t:delegate et al used often and am still trying to digest how they can
> be used effectively. For your issue, unfortunately I don't know how to
> fix it at the moment, but the problem exactly here (in Foo.java):
>
> layout.addPostWrapperBlock( _resources.findBlock( "tester" ));
>
> You've assumed that on each loop iteration, the block by id 'tester'
> will exist in its own microcosm and therefore be accessible by that id.
> In reality what I think is happening is that tapestry knows what block
> has id 'tester', and in subsequent loop iterations over your blocks I'm
> guessing that all but the last block will be replaced because of the
> hardcoded block id.
>
> Because you're looping you need to let tapestry generate the ids, but
> then of course there's the question of how to get at them. Now how to
> fix it...
>
> chris
>
> Bill Holloway wrote:
> > Hi All,
> >
> > I have a component Foo in a loop on my TestPage. Foo has a block on it
> > which Foo's template renders and which Foo's page class also picks up
> and
> > adds to a list of blocks on the TestPage's surrounding Layout component.
> > Layout loops over these blocks and renders them just before the </body>
> > tag. Problem is that the layout-rendered blocks are all the same --
> namely
> > the last block added to Layout by Foo. What am I doing wrong? Code and
> and
> > rendering results:
> >
> > Foo.java
> > ------------
> > @Property (write = false)
> > private int _ref;
> >
> > @Inject
> > private ComponentResources _resources;
> >
> > void beginRender () {
> > _ref = (new Object()).hashCode(); // For a pretty reliably random
> int.
> > Layout layout = (Layout)
> > _resources.getPage().getComponentResources().getEmbeddedComponent(
> "layout"
> > );
> > layout.addPostWrapperBlock( _resources.findBlock( "tester" ));
> > }
> >
> > Foo.tml
> > ----------
> > <t:container xmlns:t="
> http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
> > <t:block t:id="tester">
> > <p>Ref: ${ref}</p>
> > </t:block>
> > <t:delegate to="block:tester" />
> > </t:container>
> >
> > TestPage.tml
> > ------------------
> > <t:layout t:id="layout" xmlns:t="
> > http://tapestry.apache.org/schema/tapestry_5_0_0.xsd";>
> > <t:loop source="0..2"><t:test.foo /></t:loop>
> > </t:layout>
> >
> > Layout.tml (partial)
> > -------------------------
> > ...
> > <t:loop source="postWrapperBlocks" value="var:pwb"><t:delegate
> to="var:pwb"
> > /></t:loop>
> > </body>
> > </html>
> >
> > When Foo renders in TestPage's template, no problem:
> > Ref: 16084489
> > Ref: 736239
> > Ref: 9163575
> >
> > But the rendering at the bottom of Layout is
> > Ref: 9163575
> > Ref: 9163575
> > Ref: 9163575
> >
> >
>
> --
> http://thegodcode.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Those who can make you believe absurdities can make you commit atrocities.
Voltaire
