No, this is fine.  This is what Howard recommended when we asked him.  However, 
now he calls our app "mutant".  It is possible to have only one page with all 
of your components and another to swap them in and out.  One issue is that we 
have 130 "components" and I think when we create a new session for each user, 
it takes about 10 seconds to create all the components.

regards,

Mark

-----Original Message-----
From: Marcus Matèrn [mailto:[EMAIL PROTECTED]
Sent: Fri 5/12/2006 9:37 AM
To: Tapestry users
Subject: Does my "dynamic" component violate Tapestry's static structure?
 
I've created a dynamic component which renders other components based
on a "wiki" format.
This works in a similar way as Block and RenderBlock and I have not
experienced any
problems with it. Is this dynamic rendering allowed in Tapestry or
does it violate Tapestry's
static structure?

The core functionality of the component looks something like this:


protected void renderComponent(IMarkupWriter writer, IRequestCycle cycle)
{
    for (String componentName : components)
    {
        IPage page = cycle.getPage("ComponentContainer");
        IComponent component = page.getComponent(componentName);

        component.render(writer, cycle);
    }
}


Thanks!

Marcus Matèrn

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to