My advice will be to expose the remote interface of the component, so that
you can test is with standard JUnit test cases.
Its easy and you test framework is simple.
But, you have to deploy your component to JBoss
-----Original Message-----
From: Jim Crossley [mailto:[EMAIL PROTECTED]]
Sent: 10 December 2002 12:53
To: jboss-user
Subject: [JBoss-user] Testing EJB's
What's the current best practice for unit testing EJB's, (both Entity
and Session)?
I'm trying to avoid having to deploy them to a separate JBoss instance
to test them. More precisely, I want to be able to deploy them to an
in-memory container, if possible, similar to Hypersonic's in-memory
database. Ideally, the EJB container would be running within the JVM of
the JUnit test runner, persisting my CMP beans to the memory-resident
Hypersonic db.
Possible or stupid?
-- Jim
-------------------------------------------------------
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
