I found out that the described effect occurs when JBoss is started with Sun's jdk1.5.0_12 JVM. Running it with JRockit 1.5 or with Sun's jdk1.6.0_2 does not lead to this problem.
Debugging of NameScanner have shown that the method getPackage() cannot obtain a package info. | protected Package getPackage(String name) | { | try | { | Class c = classLoader.loadClass(name + ".package-info"); | return c != null ? c.getPackage() : null; | } | catch (Exception e) | { | return null; | } | } | The loadClass() method throw exceptions like this: anonymous wrote : java.lang.ClassNotFoundException: org.jboss.seam.drools.package-info As a result of this error no namespace-prefixed components are initialized in component.xml, after that lots of things go wrong. For instance, core:init component will be uninitialized, which makes that jndiPattern is not set, which in turn makes that no application components can be accessed in an EJB module. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092106#4092106 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092106 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user