AuthnRequestImpl not Serializable

[Wade, Todd]

I think what we can do is create a builder class that creates an instance of a subclass of authn request, the subclass would implement the externalizable interface and we would provide writeObject and readObject methods.

Is there suggested marshal/unmarshal implementation to use e.g. JAXB?

-----Original Message-----
From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net] On Behalf Of Chad La Joie
Sent: Thursday, November 03, 2011 4:03 PM
To: Shib Dev
Subject: Re: AuthnRequestImpl not Serializable

XMLObjects are not Java serializable, which is why they don'timplement
java.io.Serializable.  If your container puts such arequirement on
information stored in the session, then no, you can'tput XMLObjects in
that HttpSession implementation.
XMLObject themselves represent a structure that can be marshalled to
aDOM which can then be serialized to any number of formats depending
onwhat your environment supports.  You then reverse the process to
getthe XMLObject back.
On Thu, Nov 3, 2011 at 16:59, Wade, Todd <TWade at ussco.com> wrote:
> So, is there an alternative, the saml object is on our session and WebSphere
> (WAS) throws an exception when replicating also eXtreme Scale (WXS) throws
> and exception when trying to write the session to the object grid. Is the
> authn request not intended to be stored in the session?
>
>
>
> Resolution: Invalid
>
> No XMLObject is intended to be serializable.
>
>
>
> We are seeing a serialization issue due to a SAML class not being marked as
> serializable. This impacts session management. The offending class is
> org.opensaml.saml2.core.impl.AuthnRequestImpl.
>
> Please see: http://trac.accesstream.com/ticket/34
>
>
>
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered
--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net