It's most likely trying to validate that the value supplied is one of the values from the list. But that's just conjecture, since I don't use that XML Validation stuff. (*Chris*)
On Tue, Apr 12, 2011 at 12:12 PM, Eric Lentz <eric.le...@sherwin.com> wrote: > > I second Chris's suggestion to initialize the list when you need it. > > Cool getting feedback from you guys. > > I'm not sure if you meant it this way, but my point is that I don't *need* > the list - or at least I shouldn't need it IMO. > > As a user, I hit the submit button on a form that has a select list. The > select list was populated during the display. During the submit, I only > require the selected value in the select list which comes down in the > POST. > > The framework is insisting though that the list be current, but only when > I have a validation file. Again, the page works great until I put the > validation file in place and then the framework starts wanting to have the > list be populated - whether I do that populating in validate() or > prepare() - which is my current work-around, but I stress "work-around." > > - Eric
