Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3
    • Fix Version/s: 1.4
    • Component/s: None
    • Labels:
      None

      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

        Attachments

        1. WINK-388.patch
          153 kB
          Gerhard Petracek
        2. WINK-388_fixed_test_dependency.patch
          152 kB
          Gerhard Petracek

          Activity

            People

            • Assignee:
              gpetracek Gerhard Petracek
              Reporter:
              gpetracek Gerhard Petracek
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: