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