[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1991) Potential NPE in EjbReferenceResolverBase
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Tue Jan 19 02:53:47 EST 2010
[ https://jira.jboss.org/jira/browse/EJBTHREE-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaikiran pai resolved EJBTHREE-1991.
------------------------------------
Resolution: Done
> Potential NPE in EjbReferenceResolverBase
> -----------------------------------------
>
> Key: EJBTHREE-1991
> URL: https://jira.jboss.org/jira/browse/EJBTHREE-1991
> Project: EJB 3.0
> Issue Type: Bug
> Components: common, core
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: EJB3_1 1.0.2
>
>
> See JBAS-7631.
> The org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolverBase#getMatch(EjbReference reference, JBossMetaData metadata, ClassLoader cl) cannot handle null metadata. Rightly so. The code calling this method (for ex: org.jboss.ejb3.core.resolvers.ScopedEJBReferenceResolver#find(DeploymentUnit du, EjbReference reference)) must do a null check on the metadata being passed. Also update the javadoc of the EjbReferenceResolverBase#getMatch method to explicitly mention this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list