DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7751>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7751 DynaValidatorForm throws NullPointerException and ClassCastException ------- Additional Comments From [EMAIL PROTECTED] 2002-07-10 03:30 ------- What if you add a 'dynamic="true"' attribute to the form-bean element? I don't have time to set up a test scenario here, but FormBeanConfig has code which automatically sets the "dynamic" property to true when you use a DynaActionForm (by matching the implementation class name against a string.) That would explain why you get different behavior in this case. Ultimately, it looks like the null pointer exception comes from a null dynaClass property, and that property only gets initialized if the FormBeanConfig is explicitly marked "dynamic" (see RequestUtils.createActionForm(...)) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
