> -----Original Message----- > From: Derek Lin [mailto:dereklin@;hotmail.com] > > " > Clearly, the page number is the crux of the problem. That's all I was > trying to address in that fantasy syntax I was suggesting. > > What if each "form-property" element had an optional "page" attribute, > holding an integer value (or range)? At "reset" time, the only > attributes that would be reset would be the ones without a "page" > attribute, and the ones with a "page" attribute value that matches the > current "page" value. This might call for an attribute on the > "form-bean" named "pageAttribute" or "pageProperty". > " > > I thought of that. One problem with having "page" in > "form-property" is > that you are restricting the "form-property" to the "page". > What if you > want to use that "form-property" field in a different "page" for other > functions of your site? The same problem applys to the > current validator's > "page" and "field"
Certainly. You could easily find more complex needs that would make a simple declarative form not sufficient. At that point, you should be considering a non-dynamic subclass. It's impossible to satisfy everyone with a single solution. The goal is to find some solution that will make a considerable number of people mostly happy. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
