Thanks Ted. After sitting with it for a while longer, I realized that with my configuration, my dynaform needed to be of type:
org.apache.struts.validator.DynaValidatorForm rather than org.apache.struts.validator.DynaValidatorActionForm There were a few other creases, but the above seemed to be at the heart of the matter. It's working now. Although, I'm still not entirely clear about the specific differences and uses of the 2 Dyna Validator Form classes. Could you point to a resource that would help me understand this topic better? Eric On 4/7/06, Ted Husted <[EMAIL PROTECTED]> wrote: > The required validator would need to be registered, as usual. But the > rest seems OK. > > If it were me, I'd try deploying the "simplied" version as its own > application, and seeing if that works. > > -Ted. > > On 4/7/06, Eric Rank <[EMAIL PROTECTED]> wrote: > > Ted, > > > > Thanks for responding. In my real code, I have the one-to-one > > relationship set up correctly. In my efforts to make my problem as > > simple as possible for this mailing list, I neglected to change > > > > <form name="dealerSearchForm"> > > > > to read > > > > <form name="searchForm"> > > > > Assuming that the above was fixed, is there any reason why the above > > validation example wouldn't work? > > > > Eric > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
