Igor, I'm not sure whether I consider the problem that you describe as one for unit tests, at least not for me and not now. I'll have to think about it more when I'm doing EJB work again. So far, the Session Beans that I've coded have not suffered from this problem, somewhat to my surprise: I do the deployment descriptors by hand. Someday I will download and use xdoclet or try the new EJB features of IDEA 3.0 (http://www.intellij.com/idea). In the end, I think that my design approach has helped me create Session Beans that are simple enough that the likelihood of having such problems is greatly minimized.
Craig > -----Original Message----- > From: Igor Fedorenko [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 10, 2002 3:06 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Testing EJB's > > > This aproach does not test deployment descriptors. I've had > quite a few > problems with missing ejb-ref, resource-ref, etc. What is > especially bad > is that you do not know if your deployment descriptor has a problem > until you actually try to execute line of code that uses > missing resource. ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
