Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <868195512.1095094722860.JavaMail.apache@nagoya>
Date: Mon, 13 Sep 2004 09:58:42 -0700 (PDT)
From: dev@geronimo.apache.org
To: dev@geronimo.apache.org
Subject: [jira] Deleted: (GERONIMO-295) ejbLoad can not access ENC
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Message:

  The following issue has been deleted from JIRA.

---------------------------------------------------------------------

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-295
    Summary: ejbLoad can not access ENC
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Apache Geronimo

   Assignee: 
   Reporter: Dain Sundstrom

    Created: Mon, 13 Sep 2004 9:56 AM
    Updated: Mon, 13 Sep 2004 9:56 AM

Description:
The current order of the Interceptor chain returned by the EntityInstanceInterceptor does not allow to use the ENC in the context of the ejbLoad method. As depicted by the following stack trace (from Pet Store and provided by Rajesh), the ComponentContextInterceptor is not traversed prior to reach the ejbLoad method.

14:45:22,914 WARN  [SystemExceptionInterceptor] TheSignOn
javax.ejb.EJBException: SignOnDAOFactory.getDAO:  NamingException while getting DAO type :
SignonDAOClass
        at com.sun.j2ee.blueprints.signon.ejb.SignOnEJB.ejbLoad(SignOnEJB.java:117)
        at org.openejb.entity.dispatch.EJBLoadOperation.doOperation(EJBLoadOperation.java:75)
        at org.openejb.dispatch.AbstractSpecificMethodOperation.invoke(AbstractSpecificMethodOperation.java:79)
        at org.openejb.entity.dispatch.EJBLoadOperation.execute(EJBLoadOperation.java:71)
        at org.openejb.dispatch.DispatchInterceptor.invoke(DispatchInterceptor.java:72)
        at org.openejb.entity.EntityInstanceContext.associate(EntityInstanceContext.java:122)
        at org.apache.geronimo.transaction.context.TransactionContext.associate(TransactionContext.java:77)
        at org.openejb.entity.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:102)
        at org.openejb.transaction.ContainerPolicy$TxRequired.invoke(ContainerPolicy.java:123)
        at org.openejb.transaction.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:80)
        at org.openejb.SystemExceptionInterceptor.invoke(SystemExceptionInterceptor.java:82)
        at org.openejb.GenericEJBContainer.invoke(GenericEJBContainer.java:191)
        at org.openejb.proxy.EJBMethodInterceptor.invoke(EJBMethodInterceptor.java:177)
        at org.openejb.proxy.SerializationHanlder.invoke(SerializationHanlder.java:85)
        at org.openejb.proxy.EJBMethodInterceptor.intercept(EJBMethodInterceptor.java:145)
        at org.openejb.proxy.EntityEJBObject$$EnhancerByCGLIB$$d24dbfd3.getDetails(<generated>)
        at com.sun.j2ee.blueprints.petstore.control.ejb.SigninHandler.perform(SigninHandler.java:46)


Is it possible to insert the ComponentContextInterceptor just after the SystemExceptionInterceptor for the various InterceptorBuilder?


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira