I know, but unfortunatley it's not my decision to make...:)
-----Original Message----- From: Francis Amanfo [mailto:[EMAIL PROTECTED] Sent: dinsdag 4 april 2006 17:51 To: Tapestry users Subject: Re: Tapestry 3: trouble accessing Visit object Except startup issues (which I personally don't consider as big issue) I don't see any real issue that could disqualify Tap 4 as production quality software. You should be convinced by the extensive unit tests effort that were put into Tap 4 development. We're currently using it in a production environment and have not encounter any major issues. Above all, note that it's passed beta status already. Francis On 4/4/06, Bode, Bianca <[EMAIL PROTECTED]> wrote: > > We're on a project where a few developers already had some experience > with 3. > Unfortunately none of them could help me with this... > > Management decided to stick to 3. > They also believe 3 is more production stable than 4. > > What do you think? > > > -----Original Message----- > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > Sent: dinsdag 4 april 2006 17:35 > To: Tapestry users > Subject: Re: Tapestry 3: trouble accessing Visit object > > Just out of curiosity, if you're only starting off with tapestry now > why did you choose version 3 over 4? > > On 4/4/06, Bode, Bianca <[EMAIL PROTECTED]> wrote: > > > > I knew it was something awfully simple Thank you so much, eternally > > greatfull ;) > > > > -----Original Message----- > > From: Detlef Schulze [mailto:[EMAIL PROTECTED] > > Sent: dinsdag 4 april 2006 17:23 > > To: Tapestry users > > Subject: RE: Tapestry 3: trouble accessing Visit object > > > > You should use the name "org.apache.tapestry.visit-class" for the > > property in your .application file > > > > -----Original Message----- > > From: Bode, Bianca [mailto:[EMAIL PROTECTED] > > Sent: 04 April 2006 16:56 > > To: [email protected] > > Subject: Tapestry 3: trouble accessing Visit object > > > > Hi all, > > > > I've justed started with Tapestry and I have a question. > > I'm trying to store a Visit object and access it from a page. > > I have put the following in the .application file: > > > > > > <property > > name="net.sf.tapestry.visit-class">com.hp.eclaims.web.utils.Visit</p > > ro > > pe > > rty-> > > > > > > This Visit object contains a property called collectionInfo which is > > a > > > bean. > > The Visit object has a constructor that sets the collectionInfo > > property upon initialization. > > The bean properties are populated upon initialization of the bean. > > > > > > Then in the .page file, which has a corresponding class that extends > > BasePage, I'm trying to access the properties in the collectionInfo > > bean: > > > > > > <component id="pickupZip" type="TextField"> > > <binding name="value" > > expression="visit.collectionInfo.zipcode"/> > > </component> > > > > > > In my perception this should work as the getVisit() method is > > inherited from the BasePage and the getCollectionInfo() method is > > available in the Visit class and the getZipcode() method in the bean. > > > > > > Why isn't this working??? > > > > > > Hope someone can help... > > > > > > Kind regards, > > Bianca > > > > > > -------------------------------------------------------------------- > > - 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] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://opennotion.com > > --------------------------------------------------------------------- > 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]
