[
https://issues.apache.org/struts/browse/WW-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46468#action_46468
]
Amit Sharma commented on WW-3177:
---------------------------------
Still another solution would be to extend MultiPartRequest interface so that it
contains the getText() methods as in TextProvider interface. This way, the
exception can be checked inside the JakartaMultiPartRequest and the
corresponding message from the resource bundle be loaded as action error.
> i18n not supported for file upload error messages
> -------------------------------------------------
>
> Key: WW-3177
> URL: https://issues.apache.org/struts/browse/WW-3177
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7,
> 2.0.8, 2.0.9, 2.0.10, 2.0.11, 2.0.11.1, 2.0.11.2, 2.0.12, 2.0.13, 2.0.14,
> 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7
> Reporter: Amit Sharma
>
> I am troubleling with the FileUploadInterceptor in Struts2.
> I want to have printed my own messages on failure of the file upload which
> takes place in the interceptor. I am uploading files exceeding the set
> maximum size. Struts2 documentation talks about the properties
> struts.messages.error.uploading and struts.messages.error.file.too.large
> being the error message if the failure occurs or if the actual file size
> exceeds the configured maximum limit. But every time the message is something
> like <u>the request was rejected because its size (2352563) exceeds the
> configured maximum (2097152)</u>. This message comes from the
> FileUploadException that is thrown from with-in the common-fileupload class
> FileUploadBase. And In the class JakartaMultipartRequest where it is handled,
> the code in struts 2.1.6 simply adds this message in its collection of
> errors. and thus the error messages corresponding to the properties like
> <b>struts.messages.error.file.too.large</b>,
> <b>struts.messages.error.uploading</b> and
> <b>struts.messages.error.content.type.not.allowed</b> in various
> resource-bundles never gets applied.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
