Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-3726

Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0

    Details

      Description

      When starting our app in WebSphere v7.0 with seam v2.1.0.SP1, we receive the exception below
      Is it possible that annotation "javax.ejb.PostActivate" is used instead of "org.jboss.seam.annotations.intercept.PostActivate" annotation and that the former does not accept any parameter for the annotated method (At least in WebSphere v7.0) and the latter does...
      The method in question is declared as
      @PostActivate
      public void postActivate(InvocationContext invocation) throws Exception

      This method signature is present in classes SessionBeanInterceptor, EntityManagerProxyInterceptor and HibernateSessionProxyInterceptor

      Exception:
      [18/11/08 16:17:51:537 EST] 0000001a annotations E AnnotativeMetadataManagerImpl merge Caught exception while merging
      com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.persistence.EntityManagerProxyInterceptor.postActivate(Lorg/jboss/seam/intercept/InvocationContext;)V[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl@1b8e1b8e], parameters were specified, but null was the expected comparison

        Gliffy Diagrams

          Attachments

          1. jbseam-3726_2.patch
            4 kB
          2. jbseam-3726.patch
            4 kB
          3. traceback.txt
            3 kB

            Activity

              People

              • Assignee:
                pmuir Pete Muir
                Reporter:
                titou09 titou10 titou10
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: