Hi,
I have a question that relates to components and persistent variables.
This is the layout of the page I want, using frames,
with component A on frame 1 and component B on frame 2.
=== Frame 1=======|=====Frame 2========
|
A | B
|
===================================
Component A: configures colors to be seen in Component B
Component B: A picture component that needs to know the colors
selected on component A.
As I understand, each frame has it's own page, and after rendering,
the properties of the page and any components, should be set back to null
before returning to the pool.
Basically, how do i ensure component B can see the properties of component
A?
If frame 1 then frame 2 gets rendered, when component B looks at properties
for component A they will all be null (if I code according to guidelines).
Do I have to implement persistent properties on component A for this to
work?
On this topic, the docs discuss persistent properties on pages, though it
doesn't show
a full example of how this is done. It mentions HttpSession so does that
mean
I have to have a Visit object and store properties there, and then restore
the properties before the component is rendered...?
Also, at the moment I override renderComponent() and cleanupAfterRender()
in my components, though what is the distinction between
cleanupAfterRender()
and the pageDetached() methods the docs suggest for components.
ie, should I override pageDetached instead of cleanupAfterRender() ?
All comments much appreciated,
Thanks,
Patrick.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
