Excluding EJB deployment in unit test

[rkilcoyne.rkilcoyne.mac.com]

Anyone have a clean way of excluding an EJB from deployment when running unit tests? I have an MDB that uses @Depends to ensure it's deployed after Seam is started. Its dependency (jboss.web.deployment:war=/mywarname) is not deployed in the seam test environment, therefore the test environment fails to start due to the unmet dependency.

The simple, ham-handed way to fix this is to comment the @Depend annotations in all my MDBs when running unit test, but I'm sure there's a better way.

If you have suggestions, I'm all ears. Willing to trade GWT/GXT/Seam info!

RAK

[mikkus70]

I haven't tried this, but EJB specs say that the ejb-jar.xml descriptor should override class-level annotations. I would try to add an ejb-jar.xml file to the test setup.

[rkilcoyne.rkilcoyne.mac.com]

Great idea -- I'll take a look! Thanks Emir!

[rkilcoyne.rkilcoyne.mac.com]

That did it, only the <depends> tag had to be added to a jboss.xml descriptor and a couple build script changes were necessary.

[mikkus70]

Good to know, as said is not something I've tried before, so it is good info to keep handy... thanks for the feedback.

Cheers