You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Vincent Massol <vm...@octo.com> on 2001/09/22 00:05:34 UTC
[gump][cactus] cactus-23 build failures
I have succeeded in reproducing the build error. However, what's funny is
that GUMP reports the following error :
[java] [junit] Testcase: testReceiveCookie took 0.156 sec
[java] [junit] FAILED
[java] [junit] expected: but was:
[java] [junit] junit.framework.AssertionFailedError: expected: but
was:
[java] [junit] at junit.framework.Assert.fail(Assert.java:51)
[java] [junit] at
junit.framework.Assert.failNotEquals(Assert.java:234)
[java] [junit] at
junit.framework.Assert.assertEquals(Assert.java:68)
[java] [junit] at
junit.framework.Assert.assertEquals(Assert.java:75)
[java] [junit] at
org.apache.cactus.sample.TestSampleServlet.endReceiveCookie(TestSampleServle
t.java:370)
which is very strange because the source code for line 370 is :
" assertEquals("this is a response cookie", cookie.getValue());"
(any idea why ? Maybe I should try with the latest Ant too ... )
On my machine, with the Tomcat 4.0dev build from 21/09/2001 (it works with
Tomcat 4.0-b7), I get :
[java] [junit] expected:<this is a response cookie> but
was:<this+is+a+response+cookie>
[java] [junit] junit.framework.AssertionFailedError: expected:<this
is a response cookie> but was:<this+is+a+response+cookie>
which leads to the conclusion that Tomcat 4.0 has changed the way it handles
cookies ... (there are now '+' characters where before there were ' ' !). In
other words it looks like the cookies created on the server side now get
encoded ...
The problem is that all servlet engines that I have tested (Tomcat 3.3,
Resin 1.2, 1.3, 2.0, Orion 1.4, 1.5, WL 5.1, ...) all return "this is a
response cookie", meaning that I am questioning who's wrong ... :-)
Let's see what the Tomcat guys say.
Thanks
-Vincent