[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-729) Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:...

Carlo de Wolf (JIRA) jira-events at lists.jboss.org
Mon Apr 16 09:01:09 EDT 2007


     [ http://jira.jboss.com/jira/browse/EJBTHREE-729?page=all ]

Carlo de Wolf updated EJBTHREE-729:
-----------------------------------

    Fix Version/s: AS 4.2.0 GA
                       (was: AS 4.2.0 CR2)

> Injecting a EJB 2.1 bean in EJB 3 bean can show misleading warning message: IGNORING DEPENDENCY:...
> ---------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-729
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-729
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: Galder Zamarreno
>             Fix For: AS 4.2.0 GA
>
>
> An EJB 2.1 bean injected in a EJB 3 bean via:
> @EJB(mappedName="ejb/IdGenerator")
> private IdGeneratorHome idGeneratorHome;
> leads to the following warning message being logged:
> "server.log:6202:2006-10-05 14:28:36,171 WARN  [org.jboss.injection.EJBHandler] IGNORING DEPENDENCY: unable to find @EJB from interface only 
> com.acme.ejb2.uuid.IdGeneratorHome in ejb-jar.xml of SqlTimeStampBeannot used by any EJBs"
> The message is misleading as it seems to indicate that the 
> dependency was not set, but it actually did. Create call on the 
> home interface works returning a valid bean.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list