[weld-issues] [JBoss JIRA] Reopened: (CDITCK-191) double slash in Conversation test urls break redirect
[
https://issues.jboss.org/browse/CDITCK-191?page=com.atlassian.jira.plugin...
]
David Jencks reopened CDITCK-191:
---------------------------------
Rev 7124 added the testNonexistentConversationExceptionThrown method apparently ported
from trunk to the 1.0 branch, but did not include the rest of this test from CDITCK-114,
namely a filter and a change to web.xml. Rev. 7132 changed the test to apparently work
with weld without the missing parts of the test. Is adding this new method to the 1.0 tck
intentional or should it be excluded?
double slash in Conversation test urls break redirect
-----------------------------------------------------
Key: CDITCK-191
URL: https://issues.jboss.org/browse/CDITCK-191
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tests
Affects Versions: 1.0.2.CR3
Reporter: David Jencks
Assignee: Pete Muir
Fix For: 1.0.3.Final, 1.1.0.CR1
Attachments: CDITCK-191.diff
The Conversation tests all call AbstractConversationTest.getPath() with strings starting
with / such as /storm.jspx. Since the method tacks a / at the end of the context root you
end up with urls for the form foo//bar.jsf. While tomcat appears to think that this is
the same url as foo/bar.jsf, jetty doesn't. This breaks the redirect in
LongRunningConversationPropagatedByFacesContextTest.testConversationPropagatedOverRedirect.
Removing the / from the arguments to getPath fixes the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira