[
https://issues.jboss.org/browse/JBSEAM-4146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638636#comment-12638636
]
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
> "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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
