Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1225

Incorrect handling of overridden callback methods for lifecycle events

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Done
    • 1.1.5.Final, 2.0.0.Alpha3
    • 1.1.14.Final, 2.0.0.Beta1
    • None
    • None

    Description

      Weld does not follow the Interceptors spec. See also "Multiple Callback Interceptor Methods for a Life Cycle Callback Event" chapter:

      • ...
      • If a lifecycle callback interceptor method is overridden by another method (regardless of whether that method is itself a lifecycle callback interceptor method (of the same or different type)), it will not be invoked.
      • ...

      Check the following use cases:

      class Bar {
        @PostConstruct
        public void init() {
        }
      }
      class Foo extends Bar {
        @PostConstruct // Overrides Bar#init()
        public void init() {
        }
      }
      

      -> Bar#init() should not be invoked, but Foo#init() is invoked twice!

      class Bar {
        @PostConstruct
        public void init() {
        }
      }
      class Foo extends Bar {
        // Overrides Bar#init()  
        public void init() {
        }
      }
      

      -> Neither one of init() methods should be invoked, but Foo#init() is invoked!

      Right now there is no CDI TCK test for this - I will probably provide some as soon as I get familiar with the relationship of concerned specs.

      Thanks to JJ Snyder for reporting the issue.

      Attachments

        Issue Links

          Activity

            People

              rhn-engineering-jharting Jozef Hartinger
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: