[jira] [Comment Edited] (WINK-388) broken cdi integration

["Gerhard Petracek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WINK-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701003#comment-13701003 ] 

Gerhard Petracek edited comment on WINK-388 at 7/5/13 5:11 PM:
---------------------------------------------------------------

i pushed a first draft to http://s.apache.org/oqe
                
      was (Author: gpetracek):
    i pushed a first draft to https://github.com/os890/wink_patches/tree/WINK-388
                  
> 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