Hi Ture,

I think you have two options currently:

    - PageFlowUtils.addActionErrorExpression(request, "someProperty",
"${bundle.someOtherBundle.myMessage}", <args>)
    - use the 'bundleName' attribute on <netui:error>

Would either of these work for you?

Rich

p.s. var-args would be nice, huh?  Currently, the NetUI code doesn't use
Java 5 features internally, because there's a layer that lets it run
under 1.4 (with XDoclet-style annotations).  This never really became a
supported feature, and the no-Java5 restriction will end at some point.

Ture Hoefner wrote:

>Hi,
>
>  I have a case where I would like to use PageflowUtils.addActionError()
>with a message bundle other than the default bundle for the pageflow
>controller or form bean.  Would it make sense to supplement
>PageflowUtils.addActionError() with a method that takes a "bundleName" ?
>Refactoring this in PageflowUtils might not be pretty because I don't
>think you could overload the existing method because it already takes a
>bunch of Strings (by the way, var-args might be the way to go in the
>next version, if that is not already done).
>
>  Maybe we could have a method like this: 
>
> 
>
>PageflowUtils.addActionErrorUsingNonDefaultBundle( ServletRequest
>request, String propertyName, String messageKey, String bundleName,
>Object... messageArgs)
>
> 
>
> Thanks!
>
> 
>
>Ture
>
>
>  
>

Reply via email to