I wrote DynamicBlock based upon my WebObjects experience and not fully
understanding the underlying structure of the page engine in Tapestry.
DynamicBlock has big problems with things like the table component which
rely on the fact that Tapestry page structure is fixed
as the spec and template are parsed.
I'm using Block/RenderBlock extensively on my current project and they
work well. I'm even using blocks declared in separate pages to pull out
parts of a page based upon the user role. I just create a page for each
role containing the blocks and use logic to choose the page based upon a
role-to-page-map declared in a Spring config file.
Works out nice.
Please consider DynamicBlock deprecated - I will not be porting it to
T4 although the source is there for anyone who wants to take it on!
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
