Another solution is to define a generic message key in the properties file.
Something like error.generic={0}.
Then create your ActionError as new ActionError( "error.generic", "My
specific error message" );

Dave Derry

----- Original Message -----
From: "Andrew Hill" <[EMAIL PROTECTED]>
> 2.) Ah, now this is a real question!
> I had a glance at the source for the errors tag and it is here that the
key
> of the error object is used to look up the i18n message from the bundle
(ie:
> its not done in the error object itself).
> I presume your aim is to be able mix normal errors and your custom errors
> together?
> If this is the case, your best bet may well be (& there are probably
better
> ways) to create your own tag (based on errors tag) that displays both your
> custom errors and normal ones, and create your own error objects that
extend
> ActionError (and that your error tag will recognise as a custom error).
>
> -----Original Message-----
> From: Maizatulakmam Ali [mailto:[EMAIL PROTECTED]]
>
>
> I want to know how :
> 1. To display errors at specific location . Not such the normal one
> which we display the errors in a bundle.
> 2. To add custom errors instead of reading the errors from
> ApplicationResource.properties
>
> I need the answer as soon a possible.
>



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

Reply via email to