EJB 3.0
  1. EJB 3.0
  2. EJBTHREE-1246

Interceptor instances must be per EJB, not per container

    Details

    • Similar Issues:
      Show 10 results 

      Gliffy Diagrams

        Activity

        Hide
        Andrew Rubinger added a comment -

        Per EJB instance.

        Show
        Andrew Rubinger added a comment - Per EJB instance.
        Hide
        Carlo de Wolf added a comment -

        The ejb3-interceptors can run in multiple modes, two of which are AOP weaved interception (basic) and Container managed interception (direct, proxy and indirect). For EJB lifecycle callbacks to be properly handled in 'basic' mode InterceptorsFactory and InjectInterceptorsFactory are used. Both of which do nothing if used in 'container' mode and will give out a warning as such.

        For a bean developer this warning can be safely ignored.

        Show
        Carlo de Wolf added a comment - The ejb3-interceptors can run in multiple modes, two of which are AOP weaved interception (basic) and Container managed interception (direct, proxy and indirect). For EJB lifecycle callbacks to be properly handled in 'basic' mode InterceptorsFactory and InjectInterceptorsFactory are used. Both of which do nothing if used in 'container' mode and will give out a warning as such. For a bean developer this warning can be safely ignored.

          People

          • Assignee:
            Carlo de Wolf
            Reporter:
            Carlo de Wolf
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development