[ 
http://issues.apache.org/jira/browse/CACTUS-225?page=comments#action_12317616 ] 

Nicolas Chalumeau commented on CACTUS-225:
------------------------------------------

I see the link and think I can work on this...

Just a question : is this solution have some consequences/advantage for the 
cactus 2 proposal?

> Bad way of instanciating the class test a second time
> -----------------------------------------------------
>
>          Key: CACTUS-225
>          URL: http://issues.apache.org/jira/browse/CACTUS-225
>      Project: Cactus
>         Type: Bug
>   Components: Framework
>     Versions: 1.7
>  Environment: found on windows with Orion server 2.0.5 and JDK 1.4.2
>     Reporter: Romain Thouvenin

>
> According to the 'How it works' document, each test case is instanciated 
> twice. Cactus seems to use the MyTestCase(String name) constructor, but one 
> (I did) can use another constructor to instanciate its test cases.
> If this constructor initialize some fields and the default constructor does 
> not, it may (and it has) result in a NullPointerException during the test.
> When Cactus makes the second instance, it should look for other constructors 
> or some setters in order to make an exact copy of the test case.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to