Rick wrote: > Maybe I'm missing something because if you are setting this up why do > you really need to validate it? I usually only need the validation > framework for making sure the user doesn't mess up. It sounds like you > are using it to double check that you added the hidden field on the > page - but why would that need to be validated if you put it there? > Sorry if I'm missing something.
There's more to the story, but I'm still making it MUCH harder than it has to be. For various reasons I have never been able to convince a Form bean to hold all of the data that I need to manipulate. So most of my Forms are used in conjunction with a DTO which sits in session scope alongside the Form bean. (These forms are for editing fairly complex database records.) In this case, I'm not trying to make sure a form field has been filled in, I'm really trying to make sure that a property of the DTO has been set. But while Boolean seemed natural, what I really need is a String that either gets set to some text, or else left blank, and then I can just use 'required'. Thanks for being there to bounce ideas off of! I may still be completely on the wrong track, but so far, things are working. I might be able to ditch the DTO's if I could figure out nested and/or indexed properties. -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State University PA Information Resources Management
