Here is a stack trace of the problem, if it helps:
java.io.NotSerializableException: org.apache.xerces.dom.NodeListCache
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:182
2)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:47
5)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:182
2)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:47
5)
at
org.apache.xerces.dom.NodeImpl.writeObject(NodeImpl.java:1281)
at java.lang.reflect.Method.invoke(Native Method)
at
java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:18
59)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1205)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:182
2)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:47
5)
at
org.apache.xerces.dom.NodeImpl.writeObject(NodeImpl.java:1281)
at java.lang.reflect.Method.invoke(Native Method)
... Lots of classes writing out here ...
at
java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:18
59)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1205)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
at
org.apache.catalina.session.StandardSession.writeObject(StandardSession.
java:1340)
at
org.apache.catalina.session.StandardSession.writeObjectData(StandardSess
ion.java:827)
at
org.apache.catalina.session.StandardManager.unload(StandardManager.java:
507)
at
org.apache.catalina.session.StandardManager.stop(StandardManager.java:65
4)
at
org.apache.catalina.core.ContainerBase.stop(ContainerBase.java:1184)
at
org.apache.catalina.core.StandardContext.stop(StandardContext.java:3440)
at
org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:98
3)
at
org.apache.catalina.core.StandardHost.remove(StandardHost.java:789)
at
org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performUndeploy(Embedde
dCatalinaServiceSX.java:302)
at
org.jboss.web.AbstractWebContainer.undeploy(AbstractWebContainer.java:23
4)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:603)
at
org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:567)
at
org.jboss.deployment.J2eeDeployer.stopService(J2eeDeployer.java:375)
at
org.jboss.util.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:138)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(Configu
rationService.java:967)
at $Proxy0.stop(Unknown Source)
at org.jboss.util.ServiceControl.stop(ServiceControl.java:104)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.util.Shutdown.shutdownServices(Shutdown.java:87)
at org.jboss.util.Shutdown$1.run(Shutdown.java:56)
Scott
> -----Original Message-----
> From: Scott Sanders
> Sent: Tuesday, April 23, 2002 4:38 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [PATCH] Java Serialization of DOM Part 1
>
>
> So, having just completed a global search for
> "NodeListCache", I have been unable to find a possible way
> for a NodeList to actually make it to serialization.
>
> I will continue looking.
>
> Scott
>
> > -----Original Message-----
> > From: Scott Sanders
> > Sent: Tuesday, April 23, 2002 4:23 PM
> > To: [EMAIL PROTECTED]
> > Subject: RE: [PATCH] Java Serialization of DOM Part 1
> >
> >
> > We use DOM Events on some of our DOM trees, and when Catalina
> > tries to load a session from a file, it chokes saying that
> > NodeListCache is not serializable.
> >
> > I wonder if it is not transient somewhere?
> >
> > Scott
> >
> > > -----Original Message-----
> > > From: Arnaud Le Hors [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, April 23, 2002 4:01 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [PATCH] Java Serialization of DOM Part 1
> > >
> > >
> > > I'm puzzled by this one:
> > >
> > > -class NodeListCache {
> > > +class NodeListCache implements Serializable {
> > >
> > > As its name suggests this is a cache object and all
> members of this
> > > type are already declared as transient, so I don't see
> why this is
> > > needed. Not that it really hurts, but I'm curious to know why you
> > > had to add this.
> > > --
> > > Arnaud Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
