You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2013/07/05 19:11:48 UTC
[jira] [Updated] (WINK-388) broken cdi integration
[ https://issues.apache.org/jira/browse/WINK-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek updated WINK-388:
----------------------------------
Description:
list of issues:
- JCDIDefaultObjectFactory doesn't use the cdi api correctly - e.g.:
-- random behaviour in case of @Alternative and @Specializes beans
-- managing instances manually is only valid for @Dependent scoped beans
-- CreationalContext#release just destroys dependent scoped dependencies of the contextual-instance, but not the contextual-instance itself -> e.g. @PreDestroy callbacks don't get called for the contextual-instance itself
- JCDISingletonObjectFactory isn't a valid approach
-- JCDILifecycleManager only needs JCDIDefaultObjectFactory
-- keeping dependent instances as "forced singletons" should be avoided
-- during bootstrapping providers and instances of "application" need to be validated instead (of using JCDISingletonObjectFactory)
- using mocks for cdi tests, won't show real issues
-> arquillian or the test-module of OpenWebBeans should be used
was:
list of issues:
- JCDIDefaultObjectFactory doesn't use the cdi api correctly - e.g.:
- random behaviour in case of @Alternative and @Specializes beans
- managing instances manually is only valid for @Dependent scoped beans
- CreationalContext#release just destroys dependent scoped dependencies of the contextual-instance, but not the contextual-instance itself -> e.g. @PreDestroy callbacks don't get called for the contextual-instance itself
- JCDISingletonObjectFactory isn't a valid approach
- JCDILifecycleManager only needs JCDIDefaultObjectFactory
- keeping dependent instances as "forced singletons" should be avoided
- during bootstrapping providers and instances of "application" need to be validated instead (of using JCDISingletonObjectFactory)
- using mocks for cdi tests, won't show real issues
-> arquillian or the test-module of OpenWebBeans should be used
> broken cdi integration
> ----------------------
>
> Key: WINK-388
> URL: https://issues.apache.org/jira/browse/WINK-388
> Project: Wink
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Gerhard Petracek
> Fix For: 1.4
>
>
> list of issues:
> - JCDIDefaultObjectFactory doesn't use the cdi api correctly - e.g.:
> -- random behaviour in case of @Alternative and @Specializes beans
> -- managing instances manually is only valid for @Dependent scoped beans
> -- CreationalContext#release just destroys dependent scoped dependencies of the contextual-instance, but not the contextual-instance itself -> e.g. @PreDestroy callbacks don't get called for the contextual-instance itself
> - JCDISingletonObjectFactory isn't a valid approach
> -- JCDILifecycleManager only needs JCDIDefaultObjectFactory
> -- keeping dependent instances as "forced singletons" should be avoided
> -- during bootstrapping providers and instances of "application" need to be validated instead (of using JCDISingletonObjectFactory)
> - using mocks for cdi tests, won't show real issues
> -> arquillian or the test-module of OpenWebBeans should be used
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira