James Mitchell wrote:
I saw your changes to the cookie-based tests.
I did those solely because the tests were failing, and when adding debug statements I never saw any cookies actually included on the test requests.
The startup works when I switch the context path back to "test" -- silly me for thinking I could use the defined property to change this :-). The 4.1 based tests now run fine (except for a whitespace problem n TestOptionsTag1.jsp that I'm currently debugging), complete with startup and shutdown of Tomcat.Does it still hang after that?
James Mitchell Software Developer / Open Source Evangelist EdgeTech, Inc.
However, under 5.0 the startup works fine, plus the tests run to the same point, but the shutdown hangs. If I change my standard Tomcat 5.0 server.xml to use port 9005, I can use it's shutdown command to finish the shutdown, so I suspect something isn't picking up the change from the default 8005 correctly.
Craig
On Mon, 5 Jul 2004, Craig McClanahan wrote:
This is probably old news to the other developers, but hey ... just catching back up :-).
I've got the HEAD of jakarta-struts compiling fine now, but watned to run the unit tests. For either Tomcat 4.1 or 5.0, the start.tomcat.xx target seems to hang at the end of the startup, rather than proceeding on to execute the tests. Is that the currently expected behavior? Is there a workaround?
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
