Did you check in the log if .spring archive really is deployed before other stuff?
I think that changing of the MainDeployer-xmbean.xml should definitely work. I had the sam issue with different archive and it worked for me. Maybe you can have you bean that's accessing EM lazy initialized. anonymous wrote : What if i have 2 .jars which depends on each other? That's more of a Spring issue - how do you deal with cycle dependency. Maybe again lazy initialization? Rgds, Ales View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929302#3929302 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929302 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
