Adam Hardy wrote:
I don't know the JSF architecture with its "page/component state saving", Frank, but I don't think my proposition is along those lines (with state saving).
I'm no JSF expert either frankly, but I was basing my thought on the part where you said you were concerned with what happens after a validation failure and the input page being shown again... if you consider the options in a <select> to be part of the state of that component (in a sense), then I think it really is about state-saving... the only difference is that when I say "state-saving", I'm also talking about the possibility of "prepping" a component, i.e., looking up in a database for the list of <option>'s for a <select>, as one example.
Adam
Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM/Yahoo: fzammetti MSN: [EMAIL PROTECTED] Author of "Practical Ajax Projects With Java Technology" (2006, Apress, ISBN 1-59059-695-1) and "JavaScript, DOM Scripting and Ajax Projects" (2007, Apress, ISBN 1-59059-816-4) Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
