[ https://jira.jboss.org/jira/browse/EJBTHREE-1828?page=com.atlassian.jira.... ] Carlo de Wolf resolved EJBTHREE-1828. ------------------------------------- Resolution: Done -- 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

[ https://issues.jboss.org/browse/EJBTHREE-1828?page=com.atlassian.jira.plu... ] Carlo de Wolf edited comment on EJBTHREE-1828 at 1/26/11 5:11 AM: ------------------------------------------------------------------ Dependencies must never be resolved using runtime components, because these components form part of the dependency chain. The dependency chain should be setup before any runtime components are installed. This is taken care of by EjbReferenceResolver. However the EjbReferenceResolver might not have been injected yet by MC. In essence it forms a chicken/egg scenario. The handlers will at that point revert back to their legacy behavior and try to resolve that way emitting a warning in the progress. This warning can safely be ignored. was (Author: wolfc): Dependencies must never be resolved using runtime components, because these components form part of the dependency chain. The dependency chain should be setup before any runtime components are installed. This is taken care of by EjbReferenceResolver. However the EjbReferenceResolver might not have been injected yet by MC. In essence it forms a chicken/egg scenario. The handlers will at that point revert back to their legacy behavior and try to resolve that way. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira