That is correct behavior, and if you update the property (not the set
stored in the property), then the Set will be stored into the session,
and restored on the next request.
On 4/8/07, Patrick Moore <[EMAIL PROTECTED]> wrote:
Hi there --
does anyone have some thoughts on why:
@Persist
@InitialValue("new java.util.HashSet()")
public abstract Set<Long> getFollowUpMessages();
public abstract void setFollowUpMessages(Set<Long> set);
keeps on resetting the set to a new HashSet between http requests?
It looks like according to the @Persist documentation this is the correct
way to set an initial value if there is no value already in the session. But
it seems not to be the case...
-Pat
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
