>Tapestry startss with the specification, then useds that to instantiate the
>Java class.
>
>You would need to override the specification source and template source.
Would it be possible to create a new IComponent instance, an
appropriate ComponentSpecification and attach the latter to the
former?
>There are other problems; Tapestry is primarily built around a static page
>hierarchy with all the dynamic aspects you're looking for accomplished with
>conditionals and loop and the use of Block and InsertBlock.
>
>First, you've got pooling; instance of a page are pooled and there is no
>guarantee (in fact, just the opposite) that the same page instance will be
>used for two consecutive requests. Modifying the structure of the page
>complicates this because the request may rely on the specific structure of
>the page. Worse, in a clustering environment it may not be possible to
>reproduce the structure of the page in a diferent server.
Does this also apply to components? If not, I can imagine a page
with a statically configured root component, which in turn has
fully dynamic children.
What do you think about the layout manager issue?
Best regards
Rainer Klute
Rainer Klute IT-Consulting GmbH
Dipl.-Inform.
Rainer Klute E-Mail: [EMAIL PROTECTED]
K�rner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
