[
https://jira.jboss.org/jira/browse/JBSEAM-3726?page=com.atlassian.jira.pl...
]
Denis Forveille commented on JBSEAM-3726:
-----------------------------------------
I can't beleive that that this issue has once again being delayed from 2.1.2 to
2.2.0.after being delayed from 2.1.0 to 2.1.2 dispite the fact that I submit a patch ...
This prevent websphere v7.0 user to use seam.,
it seam that all the bug corrections are all towards JBoss AS and not other AS...
How long does it take to review the patch and apply it ?????
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.2.0.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@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