[
https://issues.jboss.org/browse/CDITCK-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570070#comment-12570070
]
David Jencks commented on CDITCK-191:
-------------------------------------
Ok, but could you update
http://anonsvn.jboss.org/repos/weld/cdi-tck/branches/1.0/impl/src/main/resources/tck-tests-released.xml
to indicate the actual latest release version it applies to? It says
1.0.1-Final at the moment so that's what I've been using. Better still might
be a url to the maven repo folder that contains the latest release so you can't
forget to update it again :-) Assuming that this is actually the official
exclusion list, a comment that says so would be helpful to me also.
> 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
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
