The values are stored in the session, so it is per-user. Beyond that, it is per-instance of the component. So if you have two pages that both use a @Comp with a persistent property, that's two different HttpSession attributes. If you have two different @Comp's on the same page, that's (again) two different HttpSession attributes.
Tapestry builds a key with the page name, the property name, and the component id path ... that's the HttpSession attribute key. The compnent id path is the concatenation of the component's id, and all of its parent component ids, up to the page. All components have ids, Tapestry assigns an id if you don't provide one. On 12/8/05, Dan Adams <[EMAIL PROTECTED]> wrote: > Okay, this may seem like a dumb question but just wanted to ask. > Basically, if i have a @Persist on a property in a component is the > persisted value unique per user and component instance or just per user? > For instance, say page A contains an instance of component @Comp and > @Comp has a @Persist boolean property and page B also contains an > instance of @Comp. Is it possible to set the property to true in A but > to false in B? > > -- > Dan Adams > Software Engineer > Interactive Factory > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta 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]
