"scott.stark(a)jboss.org" wrote : If the war deployer depends on the ejbs which depend on the ds, then war should be ok. | How do you define that a war depends on ejbs? Putting that horrible unnecessary xml in war.xml? Most of, if not all, Seam apps don't contain any classes in the war. It's only jsp, xhtmls, css, ... Seam initialization starts when the .war starts. The Scanner scans for components inside .ear classloader. This means it also finds components that are EJBs. If the EJB has, besides @(ejb markup annotation), also a Seam @Startup annotation, Seam will at that point try to start that component, which in this case means first looking it up in the JNDI. What about if Seam at that point added a JNDI EventListener? http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/event/NamingEv... Do support that? And got notified later on that an EJB was registered and only then continued with startup? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125803#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...