Hi Josh, What would you suggest to avoid this kind of thing. Should I rather use a primitive properties for storing form fields. It's much easier to use object but it doesn't always work the way we want it.
Thanks, Ronny joshcanfield wrote: > > The value set by the constructor, or inline, is used as the default value > for the property. When you retrieve a page from the pool it gets all of > it's > default values restored. > > Josh > > On Wed, Jul 2, 2008 at 5:21 AM, Thiago H. de Paula Figueiredo < > [EMAIL PROTECTED]> wrote: > >> Em Wed, 02 Jul 2008 09:16:19 -0300, Ronny L <[EMAIL PROTECTED]> >> escreveu: >> >> >> @Persist >>> private User user = new User (); >>> @Persist >>> private Login login = new Login(); >>> @Persist >>> private Info info = new Info(); >>> >> >> Try not initializing the fields in their declaration. Use the Form >> component prepare events to initialize them if needed. >> >> Thiago >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > -- > TheDailyTube.com. Sign up and get the best new videos on the internet > delivered fresh to your inbox. > > -- View this message in context: http://www.nabble.com/Fields-are-shared-among-application-without-using-%40Persist-tp18233088p18252072.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
