"[EMAIL PROTECTED]" wrote : So the problem seems to be that JNDI is not 
available. So I guess that the Embeddable EJB container is not properly 
started, or else your jndi.properties is missing or does not contain the 
correct values.

I am in the same boat as the other poster: this does not mean much to me either 
and I am familiar with EJB3.  Could you clarify all the requirements for 
running unit tests?  What libraries are needed, what files should be on the 
classpath and where, and so on.  As far as I can tell, my configuration is 
nearly identical to that found in the example applications, I include all the 
same libraries, my build artifacts contain the same resource files, and so 
forth.  I have been trying to pinpoint the cause but my efforts are fruitless.  
(See http://jboss.com/index.html?module=bb&op=viewtopic&t=89261 for some of my 
stack traces.)

You say our JNDI properties (may) contain the wrong values.  What should it 
contain? How is it referenced?  How does the scaffold know about the 
datasource?  What should the classpath contain?  What does the scaffold 
actually use to run the tests?  Should we be looking at the microcontainer 
configuration?  The embedded-ejb configuration?  (Note these have the same JNDI 
properties.)

I am enjoying Seam a great deal.  You guys have done a great job with this 
stuff, and I am pushing it like crazy where I work, but I really need some more 
details on debugging things like this.  I will not and cannot proceed on 
projects without unit testing, making this the only blocker on projects coming 
down the pipeline.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968415#3968415

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968415
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to