JUnit and EJBs

[Eric Hindle]

I am really new to java so I may be asking something obvious or stupid, but I am looking for the best way to run JUnit tests on EJBs with local rather than remote interfaces.
When they are being used for real, they only need to be accessed locally but JUnit needs to access them remotely (or am I wrong?)
I don't really want to define them as both local and remote just for testing purposes and if I change them after testing then I won't have tested what will be released?
Any advice would be useful.
Eric.

[Lasse Koskela]

You might want to take a look at MockEJB, which lets you test EJBs without a container (I suppose you have previously tested your EJBs by deploying them into a real EJB container?). Here's a nice little example of how you write tests using MockEJB.

[Surasak Leenapongpanit]

Did you read this "Test infect your Enterprise JavaBeans" article.

[Eric Hindle]

Thank you, and so prompt too.
Eric

[Jeanne Boyarsky]

I didn't see this in the article, but it is good to move as much business logic as possible out of the EJB and into helper classes. That way the "real" logic can be unit tested easily and the EJB can be integration tested separately.