On Sat, 19 Jun 2010 13:52:04 -0300, Inge Solvoll <inge.tapes...@gmail.com>
wrote:
Been doing a lot of searching today to find leads, and I think I got
something in BeanBlockOverrideSourceImpl.
That's where I learned how the BeanEditor/BeanEditSource blocks work. :)
Using PageRequestCache and page.getRootElement().getBlock(blockId) seems
to be a promising lead. This way I can have a Strategy service that
returns the page name that contains display blocks for the given entity
object.
You're on the right path . . .
I feel like I'm digging quite deep into the inner mechanics of Tapestry
(PageRequestCache is an internal service), but I guess there is no way to
avoid that with such advanced requirements?
Use ComponentSource instead. It uses PageRequestCache internally (can't
remember if directly or indirectly).
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
