It seems to be a bug (but I didn't find no records in jira now, so it should be a new one). I think you also noticed that the call http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-weld/7.2.0.Final/org/jboss/as/weld/injection/WeldE… made the NPE as the returned Set from type.getFields() must be null. As the 'type' comes from the loadClass call ( http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-weld/7.2.0.Final/org/jboss/as/weld/injection/WeldE… ) and as that for doesn't do any validation for null collections, I would suspect that something during the loadClass call ( http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.weld/weld-core/1.1.10.Final/org/jboss/weld/resources/ClassTran… ) might be with an issue.
What I think that might help, as the stack trace tell us that the previous call was http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… so, with log level set for debug we can see if we get this message http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… . I would also recommend to use Byteman to print the parameters and local variables before the NPE ( http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/releases/org.jboss.as/jboss-as-weld/7.2.0.Final… ) (e.g. Class<?> componentClass, Bean<?> bean, final BeanManagerImpl beanManager and AnnotatedType<?> type ). With those information we could know which exactly class and component arise the problem and how to reproduce it.
I didn't saw the picture, so could you debug and see the values of the those parameters and variables so we could have a better clue what's going on behind the scenes? Also, I would say to try other EAP versions, but I'm sure you already tested with the latest one with patches.
This is an .ear project, where we used a beans.xml in .war and .jar modules.
Removing the beans.xml from war project solved the issue, but we are not sure where is the issue.
Thanks for your assistance.
have you found any solution to this? I'm currently experiencing the same problem.....
thanks in advance