[seam-issues] [JBoss JIRA] (JBSEAM-4146) "no file extension in servlet path" exception whenever a servlet throws an exception
Matthew Lieder (Commented) (JIRA)
jira-events at lists.jboss.org
Tue Nov 1 10:02:45 EDT 2011
[ https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638817#comment-12638817 ]
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?
> "no file extension in servlet path" exception whenever a servlet throws an exception
> ------------------------------------------------------------------------------------
>
> Key: JBSEAM-4146
> URL: https://issues.jboss.org/browse/JBSEAM-4146
> Project: Seam 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.1.GA
> Environment: Java 6, Tomcat 6
> Reporter: Matthew Lieder
> Assignee: Marek Novotny
> Labels: testcase
> Fix For: 2.3.0.BETA1
>
> Attachments: SeamTestcase1.zip
>
>
> Pretty easy to reproduce: call a servlet from a Seam webapp that throws an exception, which will result in a Tomcat HTTP 500 error page that ,instead of displaying the servlet's exception, displays a "no file extension in servlet path" exception.
> See the attached testcase.
> I have yet to find a good workaround; only way seems to be to hack Seam's codebase myself. The problem definitely seems to be in org.jboss.seam.mock.MockViewHandler.getActionURL(...), as indicated by JBSEAM-2921.
--
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
More information about the seam-issues
mailing list