There were a few threads about this. You should not do this, because
pages should be static. According to Howard, this might work in a
developing enviourenment. On Production you will get problems, because
of how Tapestry Caches pages.
There are two alternatives. Either use conditional rendering
(@Conditional) or delegate the rendering to a java class: instead of
adding a component, your component calls a render method on an custom
class, passing the writer...
Cheers,
Ron
ציטוט [EMAIL PROTECTED]:
I would like to be able to add (switch out) components to a page during
runtime. I have seen a few examples on the web, however, they fall short in
binding persistent properties of the newly added component. After examining
the PageLoader class, it looks like most of the methods are private or
protected and don't allow one to mimick its operation programmatically. Is
there anyone out there who has successfully added a component during runtime
to a page and gotten the persistent properties to work? This seems to me
like a very important feature missing from the framework, unless I am
totally missing it.
Thanks,
Ozzie Gurkan
Integrated Systems Manager
Emerson Retail Services
Tel: 678-631-1925
e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
