Well, this didn't work, the header and footer from the default bundle are rendered even though there are no form validation errors, despite that the displayed error message is from the other bundle! Perhaps the errors.header and errors.footer are "inherited" from the default bundle if they are not defined in the secondary bundle?

Regardless, I am back to square one. I would appreciate any help.

Erik



Erik Weber wrote:

Seemingly a simple way to accomplish this would be to put the form validation error messages into one properties file, and to define errors.header and errors.footer for that file, and to put the non-form validation error messages into a different properties file, and to *not* define errors.header and errors.footer for that file. Then, in my JSP, I could put two html:errors tags in the error presentation area, each with a different bundle attribute:

<html:errors bundle="formValidationErrors"/>
<html:errors bundle="nonFormValidationErrors"/>

The idea is that at most one of the two would ever actually render anything.

This is what I will try unless someone has a better ideer . . . . Sorry but I find the HTML tag documentation to be far from clear, despite how great the tags are. There is probably a better way, but I need a concrete example.

Erik



Erik Weber wrote:

I am using the Validator plugin to do my form validation, and so with the <html:errors/> tag placed at the top of my content area, the form validation messages are presented, with the header and footer defined by errors.header and errors.footer. In the traditional manner, the form validation output looks something like this:

Error

Please correct these errors:

* Username is required
* Password2 must match Password1

Now, I am also presenting non-validation error messages in the same location on some pages; These are caused by Exceptions that are accounted for declaratively in struts-config.xml. The problem is, I don't want these messages to be presented with the header and footer (or maybe I want a different header and footer).

A concrete example:

For my login page, if you fail to enter a username or password, I want the error message presentation to look like the example above -- with a header and a footer (causing a table with a bulleted list to be rendered). But, if you enter the *wrong* password, and an AuthenticationException is thrown, the user ends up back at the same screen, except this time, I want the error message to be unadorned (or possibly with a different treatment), like this:

Authentication failed

As I said, AuthenticationException is handled declaratively. What is the easiest way to present the message associated with the exception *without* the header and footer in this case, while leaving the form validation error presentation (with header and footer) intact?

Thanks,

Erik


--------------------------------------------------------------------- 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]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to