"JeffBrooks" wrote : ... | Wolfc, I assume you agree with the rubbish comment and not with GColeman's comment about how disappointing JBoss 5 is. I didn't not expect such a bug to surface in CR2, so I'm just as disappointed with the situation as you guys. Not using JBoss AS 5 as a workaround, that is something I find rubbish. ;-) "JeffBrooks" wrote : anonymous wrote : So making sure the actual EJBs are not in a jar which is in lib (optionally specifying it as an ejb module in application.xml) should resolve the problem. | | Rubbish! ;-) | | Your suggestion will take significantly longer than removing two @EJB annotations. | | I'm not arguing that removing the @EJB is a good solution but in my case it is a very simple way of getting my application deployed on JBoss 5. It appears that this isn't an option for GColeman. | | What I really want is for JBoss 5 to be able to handle @EJB annotations correctly without any workarounds. | | Jeff Brooks | Yup, so far I found 2 cases where JavaEEComponentHelper throws a NPE. I want cover all bases, so we can get going without any workarounds. How come my workaround is a bigger impact? It should just be a repacking. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178739#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...