depending on what you want to test, you might get part of the way (for unit testing anyway) with easygloss.dev.java.net
it only covers injecting the resources, but with a good mocking framework you can get the important stuff tested (I wrote it, so I should know ;-) ) -Stephen On 09/11/2008, Rick <[EMAIL PROTECTED]> wrote: > I'm really having a heck of time figuring out how to EASILY test my > EJB3 components with Maven2/TestNG. I'm using the @EJB annotations to > inject EJBs into my Stateless session beans and it works fine in my > deployed ear to JBoss5. What I want to do is to test some of these > EJB3s. Some of them call other stateless session beans so it's a bit > difficult from a pure pojo approach since the whole context needs to > be set up so the EJB3 injection can take place. > > I briefly looked at EJB3Unit and I thought it look overly complicated > (but maybe I should continue to pursue that?). Using an embedded jboss > instance looked pretty easy, but the problem is this... what I'll need > to do is have my ejb jars deployed to my embedded jboss deploy > directory as part of my project. How do I tell testing in maven2 to > build jars to a deploy directory and not just target? > > Thanks for any help. > > -- > Rick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
