Return-Path: Mailing-List: contact tapestry-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tapestry-user@jakarta.apache.org Received: (qmail 48533 invoked from network); 12 Aug 2003 18:10:40 -0000 Received: from email2.byu.edu (128.187.22.134) by daedalus.apache.org with SMTP; 12 Aug 2003 18:10:40 -0000 Received: from byu079648wks.byu.edu ([128.187.136.173]) by EMAIL1.BYU.EDU (PMDF V6.2 #30538) with ESMTPA id <01KZDGOZVY088Z6ASD@EMAIL1.BYU.EDU> for tapestry-user@jakarta.apache.org; Tue, 12 Aug 2003 12:07:51 -0600 (MDT) Date: Tue, 12 Aug 2003 12:04:29 -0600 From: Dan Wells Subject: Re: PropertySelection and IPropertySelectionModel In-reply-to: <1060637573.2798.8.camel@danwells> Sender: dvw3@email.byu.edu To: Tapestry users Message-id: <1060711469.1427.12.camel@danwells> Organization: MIME-version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Content-type: text/plain Content-transfer-encoding: 7bit References: <1060637573.2798.8.camel@danwells> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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