[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3726) Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0

[Norman Richards (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460392#action_12460392 ] 

Norman Richards commented on JBSEAM-3726:
-----------------------------------------

These aren't EJB3 components/interceptors, so any any app server should definitely ignore these annotations.  That's the whole point of annotations.  

As I said, I'd like to avoid duplicating any more annotations.  Where we do further duplicate annotations, we should have a clear understanding of why we are doing it.  Right now, this appears to simply be a websphere bug, a rather large one at that.  Can you confirm that it is indeed the case that they are scanning things they shouldn't and not that we are introducing incorrectly methods on EJB3 components?  

If that's the case, then I think we can move these new annotations in as a workaround.  It would also be helpful if you (or another websphere user) could engage the developers to get them to fix this.  The whole purpose of standardizing these annotations is so that they can be reused in other contexts.  

> Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-3726
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3726
>             Project: Seam
>          Issue Type: Bug
>          Components: Platform interoperability
>    Affects Versions: 2.1.1.CR2
>         Environment: WebSphere v7.0
>            Reporter: Denis Forveille
>            Assignee: Dan Allen
>            Priority: Critical
>             Fix For: 2.1.2.CR1
>
>         Attachments: jbseam-3726.patch, traceback.txt
>
>
> 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 at 1b8e1b8e\], parameters were specified, but null was the expected comparison

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira