[
https://issues.jboss.org/browse/JBSEAM-3726?page=com.atlassian.jira.plugi...
]
Marek Novotny commented on JBSEAM-3726:
---------------------------------------
This issue was fixed in 2.1.2.CR2 so if you are trying 2.2.1.Final, you should not
experience this warning. Anyway you would rather use 2.2.2.Final which solves security
issue found in JSF EL interpolation.
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@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