Hello,
I wanted to alter the JUnitEJB classes to do just that, but since that
has already been done I'll check out the classes you pointed me to.
Thank you very much, you've been very helpful.
Scott M Stark wrote:
You can try the JBoss testsuite variation of the EJBTestCase that
allows the
jn
You can try the JBoss testsuite variation of the EJBTestCase that allows the
jndi name of the session runner to be changed per deployment and uses the
thread context class loader to load the test case rather than Class.forName
which causes problems.
See the testsuite/src/main/org/jboss/test/util/ej
Hello again, it seems the stack trace in the first attachment (and the
exception that caused it) are log4j-related, the line that triggers the
ClassCastException is the following:
[EMAIL PROTECTED] ra]$ cat src/main/org/eupki/ra/test/RASetup.java | nl -b
a| grep -w "71" -A 1
71logger
Hello list,
I'm running JBoss 3.2.1 with the 1.4.2 Sun JDK (I think it was compiled
with 1.4.1) on a Mandrake Linux 9.1 box.
Some issues with common classes between our modules led to the necessity
of using ear scoping in our ears. Now the problem is we run JUnitEJB
tests with classes in the e
