I think id is the only thing not looked up, and should be the only thing not looked up. The reason is that id is a standard attribute to set something into the page request with a certain name, and it's not dynamic anywhere else.
> -----Original Message----- > From: Erik Beeson [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 8:49 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Parameters and the ValueStack > > > I'm talking about webwork 2.0. Should everything be lookedup > on the stack? Pat's TextfieldTag currently doesn't. I just > want some clear standard to be decided upon. > > --Erik > > On Sat, 1 Feb 2003, Scott Farquhar wrote: > > > Erik, > > > > Which values are not looked up on the stack? I know that > "id" isn't > > (in iterator tag). Anything else? > > > > I don't think that this can be fixed in current webwork, as > we would > > not be able to maintain backwards compatibility? You > should add this > > as a feature to webwork 2.0. > > > > Cheers, > > Scott > > > > Erik Beeson wrote: > > > The biggest complaint that I hear about the ww taglib is > the when to > > > and when not to enclose params in single quotes. > Currently, the best > > > method for figuring this out seems to be to check the > source to see > > > if the param is ever looked up on the stack. Could there be some > > > standard agreement made as to what is and what isn't looked up on > > > the stack? Thoughts? > > > > > > --Erik > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.NET email is sponsored by: > > > SourceForge Enterprise Edition + IBM + LinuxWorld = > Something 2 See! > > > http://www.vasoftware.com > > > _______________________________________________ > > > Opensymphony-webwork mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > > -- > > > > ATLASSIAN - http://www.atlassian.com > > Expert J2EE Software, Services and Support > > ------------------------------------------------------- > > Need a simple, powerful way to track and manage issues? > > Try JIRA - http://www.atlassian.com/software/jira > > > > > > > > ------------------------------------------------------- > > This SF.NET email is sponsored by: > > SourceForge Enterprise Edition + IBM + LinuxWorld = > Something 2 See! > > http://www.vasoftware.com > > _______________________________________________ > > Opensymphony-webwork mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something > 2 See! http://www.vasoftware.com > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
