I have resolved this issue. I didn't need to use @JndiName or do anything else special
(in any case, thanks Gavin). I'm not entirely sure what the problem was but it went
away when I recreated my environment from scratch.
My problem was caused by beans not appearing at the root of the JNDI context (for some
unknown reason). I do recommend looking at your JNDI tree if you have a similar issue. If
using Embeddable EJB see
http://wiki.jboss.org/wiki/Wiki.jsp?page=EmbeddableJNDIView.
So, as far as I can see there are no issues with having multiple EJB JARs within a
Embeddable EJB 3.0 application, so long as you get the JNDI paths correct (as in Seam
documentation).
It's also important to remember to have META-INF/ejb-jar.xml and seam.properties
within the JAR. You'll also probably need to explicitly define each Entity (using
class elements) in your persistence.xml.
Dig.[/url]
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979805#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...