[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2713) Bean Annotated with @Destroy Fails on any JEE5 Certified Platform.

Burt Prior (JIRA) jira-events at lists.jboss.org
Sun Mar 9 19:38:57 EDT 2008

Bean Annotated with @Destroy Fails on any JEE5 Certified Platform.

                 Key: JBSEAM-2713
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2713
             Project: JBoss Seam
          Issue Type: Bug
          Components: EJB3
    Affects Versions: 2.1.0.A1
         Environment: Any.
            Reporter: Burt Prior
             Fix For: 2.1.0.A1

Hi Seam Team,

Per Gavin's suggestion and response to my post on the Seam Users Forum (http://seamframework.org/Community/Seam2JEE5CompliantWithTheTCKRequirements), I am submitting the following bug.

Also, please note that I collaborated with the Apache Geronimo engineers on identifying the source of the issue and the best approach to finding a resolution as well.

The following bug occurs when running the 'booking' example on the Geronimo 2.1 AS:  (please see the Users Forum entry above for the stack trace).

... 11:25:05,179 ERROR OpenEJB The bean instance business method encountered a system exception: Callback methods cannot access parameters java.lang.IllegalStateException: Callback methods cannot access parameters ...

The code in the 'booking' example that appears to cause the issue is: (on any Bean)
@Destroy @Remove public void destroy() {}

It appears that running the 'booking' (any?) Seam  (2.1.0.A1) app on the Geronimo/OpenEJB (any?) JEE5 Certified container results in the stack trace and that allowing the InvocationContext to supply the parameters during a lifecycle call results in TCK failures.

The Geronimo Engineers mentioned that if OpenEJB did not throw this exception in these circumstances it would fail the TCK.

It appears that any bean using Seam's at Destroy annotation fails on *any* JEE5 certified platform, in our case Geronimo 2.1.  We surmise, but have not verified, that this  must occur on GlassFish as well.  (Jboss 5 beta 4?)

As a test, we removed @Destroy, and still received the error.

Resolution of this error is very important to us.  I have detailed stack traces of the Geronimo log should you need them, and I would be happy to help in any way to get this issue resolved quickly.  Please don't hesitate to contact me with any questions.

Thank you for your time,

Burt Prior
IT Engineer
Cisco Systems, San Jose, CA
bprior at cisco.com

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


More information about the seam-issues mailing list