[seam-issues] [JBoss JIRA] (JBSEAM-3726) Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0
Joe Maglio (JIRA)
jira-events at lists.jboss.org
Tue May 14 10:02:06 EDT 2013
[ https://issues.jboss.org/browse/JBSEAM-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774138#comment-12774138 ]
Joe Maglio commented on JBSEAM-3726:
------------------------------------
Hello - Which version should I use to avoid this warning? We are currently using: Seam-Version: 2.1.0.GA and I have tried: Seam-Version: 2.2.1.Final
We are upgrading from WAS 6.1.0.35 to 8.5.01. IBM has indicated that this is an application issue rather than a Websphere issue.
We are not using EJBs and there does not seem to be any issue running the app.
I realize this is an old thread and closed issue, but I have recently come across this, and would like to avoid this warning during deployment. Thanks for your help.
com.ibm.wsspi.amm.validate.ValidationException: For method, org.jboss.seam.intercept.SessionBeanInterceptor.prePassivate(Ljavax/interceptor/InvocationContext;)V[com.ibm.ws.amm.scan.util.info.impl.MethodInfoImpl at 16d3046], parameters were specified, but null was the expected comparison
> Methods with an "InvocationContext" parameter annotated with "javax.ejb.PostActivate" cause a validation exception in WebSphere v7.0
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBSEAM-3726
> URL: https://issues.jboss.org/browse/JBSEAM-3726
> Project: Seam 2
> Issue Type: Bug
> Components: Platform interoperability
> Affects Versions: 2.1.1.CR2
> Environment: WebSphere v7.0
> Reporter: Denis Forveille
> Assignee: Pete Muir
> Priority: Critical
> Fix For: 2.1.2.CR1
>
> Attachments: jbseam-3726.patch, jbseam-3726_2.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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list