Hi Rob, search in this list for Dynamic Components, there are
workarounds but is not possible to dynamically instantiate components in
Tapestry due to the static nature of Tapestry page pooling mechanism.
best regards.
Raul.
Rob Dennett wrote:
I have a situation where I am passing a list of parameters to a component which
that component is iterating through and passing each list element to a
subcomponent. The list elements are objects that contain values for the
subcomponent’s parameters. Since this smacks of the DTO anti-pattern, I was
wondering if I couldn’t just instantiate the subcomponents, assign set their
properties and pass them to the component to be rendered there. Is this even
possible? It occurs to me that I would have to make sure that each one had a
unique id and that I was instantiating an instance of the concrete subclass
that Tapestry creates, so I am guessing that this is impossible. Is there in
fact a way to create a component in Java and tell another component to render
it?
Thanks,
Rob Dennett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
