Use simply the getHandle() method on the interface and the getEJBObject() on the Handle.
Handle handle=yourRemoteInf.getHandle() yourRemoteInf = (cast)handle.getEJBObject(); Andreas > -----Original Message----- > From: Sternagel Annegret (PN-SYS/PE) [SMTP:[EMAIL PROTECTED]] > Sent: 16 January 2002 11:30 > To: '[EMAIL PROTECTED]' > Subject: Re: [JBoss-user] SecurityException principal=null after bean > pass ivation > > I'm storing the interface of the SBs. > Can I find anywhere a sample how to use ejb handles ? > > Annegret > > -----Urspr�ngliche Nachricht----- > Von: Schouten, Andreas [mailto:[EMAIL PROTECTED]] > Gesendet: Mittwoch, 16. Januar 2002 10:42 > An: [EMAIL PROTECTED] > Betreff: RE: [JBoss-user] SecurityException principal=null after bean > pass ivation > > > Do You store the a reference of the Interface of SB or the bean handle? > > The was a bug in an older version (2.4.x ??) with references to SB's. > Useing > ejb handles should solve this. > > Andreas > > > -----Original Message----- > > From: Sternagel Annegret (PN-SYS/PE) > [SMTP:[EMAIL PROTECTED]] > > Sent: 16 January 2002 10:19 > > To: [EMAIL PROTECTED] > > Subject: [JBoss-user] SecurityException principal=null after bean > > passivation > > > > Hi, > > > > I have a secured stateful SessionBean with references to one or more > other > > secured stateful SessionBeans stored in a Hashtable. If the bean has > been > > passivated and the AuthenticationCache timer in the JaasSecurityManager > > has > > expired I get a SecurityException on the next bean access: > > > > [SubscriberSB] Authentication exception, principal=null > > [SubscriberSB] TRANSACTION ROLLBACK EXCEPTION:checkSecurityAssociation; > > nested exception is: > > java.lang.SecurityException: Authentication exception, > > principal=null; nested exception is: > > java.rmi.RemoteException: checkSecurityAssociation; nested exception > > is: > > java.lang.SecurityException: Authentication exception, > > principal=null > > [SubscriberSB] java.rmi.RemoteException: checkSecurityAssociation; > nested > > exception is: > > [SubscriberSB] java.lang.SecurityException: Authentication > > exception, > > principal=null > > [SubscriberSB] java.lang.SecurityException: Authentication exception, > > principal=null > > [SubscriberSB] at > > > org.jboss.ejb.plugins.SecurityInterceptor.checkSecurityAssociation(Securit > > yI > > nterceptor.java:168) > > [SubscriberSB] at > > > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.j > > av > > a:92) > > ... > > > > If the beans references to other secured beans have not been initialised > > it's working fine. > > What's going on ? > > Do I have to do something in ejbPassivate / ejbActivate concerning the > > bean > > references ? > > > > Thanks in advance > > Annegret > > > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
