I did some further testing and found out that this problem only occurs when "Reload test-classes" is enabled. This might explain the difference between the SwingUI/TextUI and 3.2 which did not feature reloading of testclasses.
I'm still wondering how reloading testclasses could cause this problem though.
From: Gustav Bostrom
Sent: Monday, February 25, 2002 12:06 PM
Subject: Problem calling EJBs(JBoss) from JUnit 3.7 SwingUI, works in 3.2 and 3.7 TextUI
I'm aware that this is not really a development question, but I'm not sure where else to turn.
I'm experiencing an extremely weird problem when running JUnit 3.7 Swing UI when I'm testing EJBs running in JBoss.
I get this error:
Admittedly this is not an error in the JUnit code, however what really puzzles me is that I do not get this error when running JUnit 3.7 TextUI!
The error is not present in JUnit 3.2 either in the TextUI or the SwingUI. So, I'm absolutely positive that this is not a problem in the test setUp() code.
If anyone can tell me what is wrong here I would be very thankful!
Any hint on how to get this to work would be great. For now we are forced to use JUnit 3.2 instead of 3.7 which is of course not what we want especially since we want to move to JDK 1.4
the eon company