[
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.
"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