how about another attribute, i.e.,
<html:form checkFormBean="false" ...
The checkFormBean defaults to true so it is backwards compatible with other versions.
I like the idea that html:form checks for the form bean. It makes it easier to debug the way it is. However, I can see when you would not want that....
Well, I'm figuring that if you actually NEED the form bean, then something else would throw an exception; presumably the first input tag which isn't backed by some explicitly named bean.
I'd probably leave out the parameter in preference of error checking at the right spot. I think what Ted was getting at in his email was that other tags might not be doing good error checking because they've always deferred to html:form -- and yes, it would be bad to remove the check and then start having NPEs thrown that might be much harder to debug.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]