[ https://jira.jboss.org/jira/browse/JBSEAM-4146?page=com.atlassian.jira.pl... ] Kenneth Christensen commented on JBSEAM-4146: --------------------------------------------- I have the same problem. I'm using url rewriting and the exception is triggered when Seams multipart filter throws an exception because the size of the uploaded file is too big. components.xml: ... <web:multipart-filter create-temp-files="true" max-request-size="1000000" url-pattern="/*"/> ... Stacktrace ("org.jboss.seam.web.FileUploadException: Multipart request is larger than allowed size" is swallowed by Seam): 12:03:12,438 ERROR [BaseXMLFilter] Exception in the filter chain javax.servlet.ServletException: java.lang.IllegalArgumentException: no file extension in servlet path: /UpdateDistributor at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:126) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.IllegalArgumentException: no file extension in servlet path: /UpdateDistributor at org.jboss.seam.mock.MockViewHandler.getActionURL(MockViewHandler.java:45) at org.jboss.seam.jsf.SeamViewHandler.getActionURL(SeamViewHandler.java:74) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:168) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:55) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:42) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51) at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) ... 33 more 12:03:12,439 ERROR [[default]] Servlet.service() for servlet default threw exception java.lang.IllegalArgumentException: no file extension in servlet path: /UpdateDistributor at org.jboss.seam.mock.MockViewHandler.getActionURL(MockViewHandler.java:45) at org.jboss.seam.jsf.SeamViewHandler.getActionURL(SeamViewHandler.java:74) at org.jboss.seam.faces.FacesManager.redirect(FacesManager.java:168) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:55) at org.jboss.seam.faces.Navigator.redirect(Navigator.java:42) at org.jboss.seam.exception.RedirectHandler.handle(RedirectHandler.java:51) at org.jboss.seam.exception.Exceptions.handle(Exceptions.java:76) at org.jboss.seam.web.ExceptionFilter.endWebRequestAfterException(ExceptionFilter.java:114) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:70) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4146?page=com.atlassian.jira.pl... ] Matthew Lieder commented on JBSEAM-4146: ---------------------------------------- This problem is still in Seam 2.0.0.GA and has really been annoying us :/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4146?page=com.atlassian.jira.pl... ] Norman Richards reassigned JBSEAM-4146: --------------------------------------- Assignee: Norman Richards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4146?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-4146: ------------------------------ Assignee: (was: Norman Richards) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4146: ---------------------------------- Fix Version/s: (was: 2.2.1.Final) sorry, but 2.2.1.Final will fix only bugs found in previous 3 Candidate Releases. I promise to look in for next release. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4146: ---------------------------------- Assignee: Marek Novotny Fix Version/s: 2.3.0.BETA1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4146: --------------------------------------- I can see here a little confusion/misunderstanding. Just to be sure that I understand the issue correctly. You get an exception while calling servlet and redirection of request (due exception) is checking whether it is used suffix/prefix mapping in servlet mapping. It evaluates like suffix mapping, so it supposes that you should have there /*.seam instead of /servlet/exception. That is what the exception says - Seam expects servlet mapping /servlet/exception.seam and in your servlet mapping is no suffix mapping *.seam. And that can be proved if you change the servlet mapping to /servlet/exception.seam. Also the attached test case has got a mistake in error handling page definition in page.xml (there is message.xhtml instead of error.xhtml). Anyway it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Matthew Lieder commented on JBSEAM-4146: ---------------------------------------- Yes, that sounds like a good understanding of the issue -- Seam is making a wrong assumption that servlet mappings always end in .seam. If this was a brand new app I was creating I'd simply work around this bug by adding .seam to my servlet mappings, but since it's a few years old and there are deep links to the servlets in many different other systems it wouldn't be worth all the pain it would cause. Maybe I could hack around it with url-rewrite, though that would be a bit ugly. Are you committed to fixing this bug? Will it be reasonably easy for you to fix? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Matthew Lieder commented on JBSEAM-4146: ---------------------------------------- Awesome; appreciate it :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny edited comment on JBSEAM-4146 at 11/3/11 9:19 AM: ---------------------------------------------------------------- I have looked deeply into fixing this and the solution is not fully clean, but you can handle your old applications. First this is not bug for Seam, because all what you want to handle by Seam should be mapped to {noformat}*.<suffix>{noformat} or with help of rewrite-filter to something like {noformat}<web:rewrite-filter view-mapping="/servlet/*" />{noformat}. Anyway I lower the IllegalArgumentException and try to redirect to viewId if not found correct suffix. You have to only map correctly your error page in page.xml to the recognized url-pattern for FacesServlet. In the attached example testcase you have to map to error.seam instead of error.xhtml. P.S. actually the attached example has got in page.xml message.xhtml, but that is mistake. If it is not what you want, I will cancel the fix. was (Author: manaRH): I have looked deeply into fixing this and the solution is not fully clean, but you can handle your old applications. First this is not bug for Seam, because all what you want to handle by Seam should be mapped to *.<suffix> or with help of rewrite-filter to something like <web:rewrite-filter view-mapping="/servlet/*" />. Anyway I lower the IllegalArgumentException and try to redirect the directly viewId if not found correct suffix. You have to only map correctly your error page in page.xml to the recognized url-pattern for FacesServlet. In the attached example testcase you have to map to error.seam instead of error.xhtml. P.S. actually the attached example has got in page.xml message.xhtml, but that is mistake. If it is not what you want, I will cancel the fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Matthew Lieder commented on JBSEAM-4146: ---------------------------------------- Thanks Marek. I played around with using rewrite-filter a bit but still couldn't get it working -- the code in getActionURL(...) is looking at getRequestServletPath() which isn't affected by the rewrite so it's still /servlet/exception since that's what the user's browser is pointed that. Basically anything that makes the test case work while still keeping the seam filter enabled over the entire app (the servlets I have make use of Seam) is acceptable to me. I'll try out the latest snapshot build with your fix on this test case as soon as I can and get back to you with my results. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4146: --------------------------------------- The fix is starting from today at snapshot repository, specifically this is the first built jar https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-4146. ----------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira