[
https://issues.apache.org/jira/browse/OWB-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bergmark resolved OWB-630.
------------------------------
Resolution: Fixed
> AmbiguousResolutionException thrown for Decorators that Decorate multiple
> beans where any of those beans are passivation capable.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: OWB-630
> URL: https://issues.apache.org/jira/browse/OWB-630
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Interceptor and Decorators
> Affects Versions: 1.1.2
> Reporter: Joe Bergmark
> Assignee: Joe Bergmark
> Fix For: 1.1.3
>
>
> BeansDeployer generally does the right thing and doesn't attempt to ensure
> that @Delegate injection points only resolve to a single bean.
> However, if you have a Decorator that decorates a passivating scope bean
> (@SessionScoped, @ConversationScoped, etc), then as part of validating that
> the Decorator is also passivization capable we call into WebBeansUtil
> isPassivationCapableDependency(InjectionPoint injectionPoint)
> That method attempts to resolve the InjectionPoint to ensure it resolves to a
> bean that can be passivated, but it should not attempt to do this for
> injection points containing @Delegate as by definition those can resolve to
> multiple beans. In fact, we will never even get to this point if we were not
> decorating a passivization capable bean.
> I have a unit test that re-creates this problem, and I believe there is a
> very simple fix to WebBeansUtil to check for the @Delegate annotation on the
> injection point.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
