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/ejb package in the current 3.2 cvs tree. The 3.2.2RC4 release includes this as well, but that version is still using the Class.forName call.
-- xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
Stefan Puiu wrote:
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
71 logger = (EupkiLogger)EupkiLogger.getLogger(
72 RASetup.class.getName());
Anyway, I still have the packaging issue which is now solved by putting only the junitejb.jar (which is 7 KB large) in the ear. However, if I package JUnitEJB in each ear then I'd get a JNDI name clash when deploying all modules, so it's not a good solution. Other suggestions?
Stefan Puiu wrote:
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
