PropertySelection and IPropertySelectionModel

[Dan Wells <da...@byu.edu>]

Hi all,

I've read the docs, and checked the mail archive, but I would like to
understand the PropertySelection component and the
IPropertySelectionModel interface better.

Does tapestry then save the model object into the session, so that when
it translates the value back into the object to set the property
specified as the value parameter it still has the list of objects?  If
so, how can I use a Select drop-down box in a State-LESS application? 
Would that be a case where I have to use the Select and Option
components?  Or is there a way to still have the ease of the
PropertySelection object, without objects being stored into the session?

-- 
Dan Wells <da...@byu.edu>

Re: PropertySelection and IPropertySelectionModel

[Dan Wells <da...@byu.edu>]

Nevermind, that was a stupid question.  It just hit me that I was a
little confused.  Whether the model is stored in the session is up to
me, as I can make it a property of my visit, engine, page, or component.


On Mon, 2003-08-11 at 15:32, Dan Wells wrote:
> Hi all,
> 
> I've read the docs, and checked the mail archive, but I would like to
> understand the PropertySelection component and the
> IPropertySelectionModel interface better.
> 
> Does tapestry then save the model object into the session, so that when
> it translates the value back into the object to set the property
> specified as the value parameter it still has the list of objects?  If
> so, how can I use a Select drop-down box in a State-LESS application? 
> Would that be a case where I have to use the Select and Option
> components?  Or is there a way to still have the ease of the
> PropertySelection object, without objects being stored into the session?
-- 
Dan Wells <da...@byu.edu>