Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-3554

ejb-jar.xml interceptor-binding does not accept "*"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • 8.2.0.Final, 9.0.0.Alpha1
    • 8.1.0.Final
    • EJB
    • None
    • Hide

      Add a ejb-jar.xml to a simple ejb3 application with the following content:
      <ejb-jar>
      <assembly-descriptor>
      <interceptor-binding>
      <ejb-name>*</ejb-name>
      <interceptor-class>wfink.Dummy</interceptor-class>
      </interceptor-binding>
      </assembly-descriptor>
      </ejb-jar>

      The Interceptor must not exist, it will cause a ClassNotFoundEx if "*" is replaced by a valid bean name

      Show
      Add a ejb-jar.xml to a simple ejb3 application with the following content: <ejb-jar> <assembly-descriptor> <interceptor-binding> <ejb-name>*</ejb-name> <interceptor-class>wfink.Dummy</interceptor-class> </interceptor-binding> </assembly-descriptor> </ejb-jar> The Interceptor must not exist, it will cause a ClassNotFoundEx if "*" is replaced by a valid bean name

    Description

      From the ejb3.1 specification (JSR 318) chapter 12.7 Specification of Interceptors in the Deployment Descriptor:
      ""
      In the interceptor-binding element, the target-name element must be the name of one of
      the enterprise beans contained in the ejb-jar or the wildcard value “*”.
      ""

      But the "*" as ejb-name is ignored, only a bean name will result in binding the interceptor during deployment

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-6292 A Warning should be logged if an interceptor is ignored because of missing configuration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: