On 2/25/07, Colin Chalmers <[EMAIL PROTECTED]> wrote:
1. The browser Back-button
when the user clicks on the browser back-button he should be taken
back a page without loss of data .
I've seen comments about client/side state saving in connection with
cache expiry settings
I've also seen solutions based on seam & shale.
Can someone comment on this as to what works for them?
What works for me is client-side state saving with no "important"
session-scoped data. Ie, anything stored in session scope can be
trivially and automatically recreated if the session goes away. The
application can be restarted (and sometimes even updated if the
serailization doesn't change) without the end-user noticing.
2. Bookmarking pages
3. Google findable
no experience.
4. Initializing data-sources
We had an ugly workaround to init/destroy data in backing-beans. I
see that Shale has methods for this (aptly called init/destroy)
How do others do this with *basic* myfaces to ensure that data is
retrieved once during the life-cycle?
initialization is simple -- make a setInitialize(Object value)
accessor on the managed bean, and put the following managed property
LAST. Your setInitialize() method will be called right after all
other managed beans have been set.
<managed-property>
<property-name>initialize</property-name>
<value>initialize</value>
</managed-property>
I have also used spring-bean-based init/destroy methods in the past.
