[seam-issues] [JBoss JIRA] Updated: (JBSEAM-4146) "no file extension in servlet path" exception whenever a servlet throws an exception
[
https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugi...
]
Matthew Lieder updated JBSEAM-4146:
-----------------------------------
Fix Version/s: 2.2.1.Final
(I know this isn't the proper thing to do, but this issue has been continually
annoying us for the past year and I want to make sure this gets to a Seam developer's
attention; they don't seem to look through user-reported issues much. There's a
testcase and everything included, so it shouldn't take much time 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
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Java 6, Tomcat 6
Reporter: Matthew Lieder
Labels: testcase
Fix For: 2.2.1.Final
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira