In answer to Russ Baker's question ("Trouble getting ServletConfig" thread),
I have been spending the last few hours adding support for Orion 1.5.2 to
Cactus. I am almost done and the tests run fine (no missing parameter
errors) except one and I don't know why. It looks real strange as it seems
there is a side effect involved. My turn to ask for help :)

Here is the console trace I get :

    [java]     [junit] Running
org.apache.commons.cactus.sample.unit.TestServletTestCase5
    [java]     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
0,781 sec
    [java]     [junit] Testsuite:
org.apache.commons.cactus.sample.unit.TestServletTestCase5
    [java]     [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed:
0,781 sec
    [java]     [junit]
    [java]     [junit] Testcase: testTearDown took 0,771 sec
    [java]     [junit] Running
org.apache.commons.cactus.sample.unit.TestServletTestCaseSpecific
    [java]     [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0
sec
    [java]     [junit] Testsuite:
org.apache.commons.cactus.sample.unit.TestServletTestCaseSpecific

    [java]     [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0
sec
    [java]     [junit]
    [java]     [junit] Running
org.apache.commons.cactus.sample.unit.TestJspTestCase
    [java]     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed:
0,761 sec
    [java]     [junit] Testsuite:
org.apache.commons.cactus.sample.unit.TestJspTestCase
    [java]     [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed:
0,761 sec
    [java]     [junit]
    [java]     [junit] Testcase: testOut took 0,751 sec
    [java]     [junit]         Caused an ERROR
    [java]     [junit] testTearDown() worked
    [java]     [junit] junit.framework.AssertionFailedError: testTearDown()
worked
    [java]     [junit]         at
org.apache.commons.cactus.sample.unit.TestServletTestCase5.tearDo
n(TestServletTestCase5.java:137)

What is strange is that the tests of TestServletTestCase5 seem to run fine
and the error seems to be in TestJspTestCase ...
However the exception "testTearDown() worked" is an exception I throw on
purpose in TestServletTestCase5.tearDown() !!!

So far, I have no idea and will need to debug ...

Also, it seems that version 1.5.2 is not supporting the jsp-file tag anymore
in web.xml. Is that true ? When I use such a mapping for the JspRedirector
it fails and if I use a jsp file in cactus.properties instead it works
(cactus.jspRedirectorURL =
http://localhost:@test.port@/test/test/redirector.jsp) ....

Thanks
-Vincent

Reply via email to