[
http://jira.jboss.com/jira/browse/JBSEAM-1239?page=comments#action_12365153 ]
Christian Bauer commented on JBSEAM-1239:
-----------------------------------------
Can the multipart filter run after the exception filter, so we can use pages.xml exception
handling?
Throw distinquishable exception type if size limit of
MultipartRequest is exceeded
----------------------------------------------------------------------------------
Key: JBSEAM-1239
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1239
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Christian Bauer
Assigned To: Shane Bryzak
Priority: Minor
Fix For: 1.3.0.ALPHA
java.lang.RuntimeException: Multipart request is larger than allowed size
org.jboss.seam.web.MultipartRequest.<init>(MultipartRequest.java:282)
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:74)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
I can't catch this and display a proper error message. Also the pages.xml exception
handling doesn't catch it, since it happens too early in a filter. If there is any
reasonable way we need to make this exception case more customizable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira