Well, I won't say that I've made that mistake twice....;) I am glad to hear you got it running!
Chris > -----Original Message----- > From: Stuart Townhill [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 1:29 PM > To: 'Turbine Users List' > Subject: RE: Intake - Not sure? > > > Chris, > > Thanks again, you wouldn't believe it, after correctly writing my screen > class, template and action class all I forgot to do was implement the > Retrievable Interface. Wont' be making that mistake again. (There was no > sign of any useful error in the log though) But looks like I've got the > basics of intake figured was thinking about looking at the Validator tag > for creating some custom rules. > > Regards, > > Stuart Townhill. > > -----Original Message----- > From: Chris K Chew [mailto:[EMAIL PROTECTED] > Sent: 12 March 2003 22:48 > To: Turbine Users List > Subject: RE: Intake - Not sure? > > Hi Stuart. > > Just to be sure I understand your problem: The form works with a new > job > ($Jobgroup=$intake.Jobgroup.Default), but not when mapping an existing > $editjob? > > If so, then it looks like something is keeping the mapto($editjob) from > mapping properly. This would make $jobgroup null, which explains the > Velocity log entry and the form output. Intake should log such errors > into > Turbine.log, is there anything in there? Common ones I get are that it > couldn't find the get/set method for one of the fields, a mismatching > value > type for one of the get/set methods, or the $editjob object doesn't > implement Retrievable. > > Chris > > > -----Original Message----- > > From: Stuart Townhill [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 12, 2003 3:13 PM > > To: 'Turbine Users List' > > Subject: RE: Intake - Not sure? > > > > > > Bill, > > > > Yes all the values that should be entered into the input fields are > > rendered to the screen: > > > > Job Details: $editjob.CustomerId, $editjob.QuotationId etc. > > Becomes: > > Job Details: 1000, 1001 etc. > > > > They just don't seem to mapTo correctly. > > > > > > My input fields are rendered as: > > > > <INPUT TYPE="text" size="30" name="$Jobgroup.Quotationid.Key" > value=""/> > > Instead of something like: > > <INPUT TYPE="text" size="30" name="Jobgroup_0Quotationid" > value="1001"/> > > > > And my validation statements fail and render the variable names to the > > screen i.e. $Jobgroup.Customerid.Message > > > > #if (!$Jobgroup.Customerid.isValid()) > > <TD> > > #errorMessage("$Jobgroup.Customerid.Message") > > </TD> > > #end > > > > Regards, > > > > Stuart Townhill. > > > > > > > > -----Original Message----- > > From: Bill [mailto:[EMAIL PROTECTED] > > Sent: 12 March 2003 09:34 > > To: Turbine Users List > > Subject: Re: Intake - Not sure? > > > > Stuart > > > > > I can access all the fields as can > > > bee seen on the third line of my code so everything is correctly > > > delivered by the screen class via the context. > > > > Are you saying that the screen renders and the variables that are > > represented by the third line of code are visible on the page with the > > correct values? > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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] > > > > --------------------------------------------------------------------- > 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]
