That's fine, the security context of a call is stateless.
- Original Message -
From: "Jules Gosnell" <[EMAIL PROTECTED]>
To: "Ignacio Coloma" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, January 14, 2002 2:28 PM
Subject: Re: [
je original-
> > De: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]En nombre de Jules
> > Gosnell
> > Enviado el: sabado, 12 de enero de 2002 13:55
> > Para: [EMAIL PROTECTED]
> > Asunto: [JBoss-dev] java.io.NotSerializableException:
> > org.jboss.jet
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 12, 2002 5:55 AM
Subject: [JBoss-dev] java.io.NotSerializableException:
org.jboss.jetty.JBossUserRealm
>
> Marc,
>
> My understanding of this Exception popping up in the web testsuite was
> that serialisat
Jules, the fix is very easy, you don't have to make JBossUserRealm
serializable, instead, when you do
SecurityAssociation.setPrincipal() don't pass it 'this' which is
JBossUserPrincipal, rather pass along a new SimplePrincipal() which
corresponds to the name stored in JBossUserPrincipal. The JBos
Marc,
My understanding of this Exception popping up in the web testsuite was
that serialisation was occuring because optimisation was not. Therefore
I have not invested time in the alterations to JBossUserRealm to make it
Serializable.
What is the situation here? Is this still the case - or doe
