Yes, the offending class seems to be the Struts RequestProcessor.
-----Original Message----- From: Leticia Golubov [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 13, 2004 2:26 AM To: Struts Users Mailing List Subject: RE: REQUEST_PROCESSOR - couldn't deserialize I've had a similar problem before when the offending class did not implement java.io.Serializable... regards Leticia -----Original Message----- From: Gopalakrishnan, Jayesh [mailto:[EMAIL PROTECTED] Sent: 12 January 2004 18:54 To: Struts Users Mailing List Subject: REQUEST_PROCESSOR - couldn't deserialize Has anybody encountered this exception...? <Jan 6, 2004 8:39:01 PM EST> <Error> <HTTP> <BEA-101309> <[ServletContext(id=158851062,name=stap-portal,context-path=/stap-portal)] could not deserialize the context attribute "org.apache.struts.action.REQUEST_PROCESSOR" java.io.NotSerializableException:org.apache.struts.tiles.TilesRequestProcess or at java.io.ObjectOutputStream.writeObject0(Ljava.lang.Object;Z)V(Unknown Source) at java.io.ObjectOutputStream.writeObject(Ljava.lang.Object;)V(Unknown Source) at weblogic.servlet.internal.AttributeWrapper.getObject(Z)Ljava.lang.Object;(At tributeWrapper.java:95) at weblogic.servlet.internal.AttributeWrapper.getObject()Ljava.lang.Object;(Att ributeWrapper.java:67) at weblogic.servlet.internal.WebAppServletContext.getAttribute(Ljava.lang.Strin g;)Ljava.lang.Object;(WebAppServletContext.java:637) at org.apache.struts.action.ActionServlet.getRequestProcessor(Lorg.apache.strut s.config.ModuleConfig;)Lorg.apache.struts.action.RequestProcessor;(ActionSer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]