[jboss-dev-forums] [Design of EJB 3.0] - Re: BeanContainer.getAnnotation returning the old value

By any chance has any further development happened on this issue or its patch? It looks like JBoss 5.1.0-GA incorporates this patch, but I'm running into a NullPointerException in org.jboss.metadata.annotation.creator.ejb.jboss.RolesAllowedProcessor within the added code. This bit: if (existingMethod.getMethodName().equals(mmd.getMethodName()) | && existingMethod.getMethodParams().equals(mmd.getMethodParams())) | { | // Do nothing | return; | } When a method comes in with zero parameters (the exitingMethod MethodMetaData object toString() looks like "MethodMetaData(ejbName=EntitySessionBean,interface=null,method=*,params=null)", JBoss throws NPE on deployment when the exitingMethod.getMethodParams() call returns null and .equals() on that blows up. I haven't entirely ruled out some deployment and/or packaging problem with the application, but I'm not sure how best to figure that out. The app deploys fine under JBoss-4.2.3.GA, and there are no other messages even at TRACE level logging that point to a packaging problem. The app is using EJB3 annotations of course and is overriding some elements in both ejb-jar.xml and jboss.xml. Both of those pass schema validation using the jboss_5_0.xsd schemas. Any guidance would be much appreciated. Best regards, Zac Bedell New York State Unified Court System View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236846#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...