Em Wed, 04 Mar 2009 00:00:28 -0300, Luther Baker <lutherba...@gmail.com>
escreveu:
I took a look and found this page on COMPONENT rendering:
http://tapestry.apache.org/tapestry5/guide/rendering.html and I tried the
literal method
void setupRender
In which class have you declared this method? If it was the page where you
put your edit and view blocks (let's call it BlocksPage), it wouldn't
work, as BlocksPage is never rendered (never requested), just blocks and
components declared inside it are. BlocksPage just exists because all
Tapestry blocks needs to be declared inside some page.
Does an edit block act like a page and not a component?
A block is not a page nor a component. @PageAttached just worked because
you declared it inside a page.
And, am I missing something or is a PAGE lifecycle signficantly different
than a COMPONENT lifecycle?
A page is a component. It has the component lifecycle plus some events of
its own.
I had read and made the assumptions that PAGEs
were actually COMPONENTs themselves and because they are special maybe I
could see a PAGE having *additional* lifecycle methods -
This is absolutely correct.
but I wasn't ready for none of the COMPONENT lifecycle methods to trip.
Again: a page used just to provide blocks does not react to component
lifecycle events because it is not being rendered (it was not requested),
just one of its blocks.
I strongly suggest you to learn about events in Tapestry using writing
very normal page (one that really renders HTML) and writing a simple
component. Writing blocks for BeanEditForm/BeanEditor is a very confusing
place to learn about them. ;)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
