Looking in my code, I never set the initial value of a persistent property to something non-trivial - always null - so I can't help, other than to offer the .page or .jwc file, since you can certainly do it in there, or else to initialize without an annotation. If you put your init code in pageAttached(), it fires very early in the cycle and only fires once for each request. Unfortunately, it fires after tap populates the property from the session (I think), so you'll have to test for non-triviality before shoving a new value in it.
Or just fix the annotation, I suppose. --sam On 12/7/06, Dan Adams <[EMAIL PROTECTED]> wrote:
So, how do you set the initial value of a Persisted property to something non-trivial? On Thu, 2006-12-07 at 17:58 +0100, Ron Piterman wrote: > Yes, it doesn't seem they work together - for me too... (on t4.0) > Cheers, > Ron > > Dan Adams wrote: > > I've ran into a problem that other people seem to have reported on the > > mailing list before. But my unanswered question is: if you use @Persist > > and @InitialValue, when does the value get set back from the session? > > I've got the same problem someone else did where the property is set to > > the same value every time. Thanks. > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
