Prashant, Notice java.util.ArrayList.writeObject in the stack trace. It appears as though the exception is being thrown when it is trying to serialize an object in a List, not the object which to which the List is a propery of.
Dennis Byrne >-----Original Message----- >From: Nagaraddi, Prashant [mailto:[EMAIL PROTECTED] >Sent: Friday, April 21, 2006 04:28 PM >To: 'MyFaces Discussion' >Subject: RE: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT > >Here is the full stack trace. It seems to be happening in the render lifecycle >phase. Threre is only one definition of the class. However, there is an inner >classes defined inside of MyIpaList called PartyNameMap. PartyNameMap also >implements the serializable interface and has a default no-arg constructor. I >am not sure if that is causing the problem. > >ERROR JspStateManagerImpl - Exiting deserializeView - Could not deserialize >state: amazon.merchants.ipa.workflow.backingbeans.MyIpaList; no valid >constructor >java.io.InvalidClassException: >amazon.merchants.ipa.workflow.backingbeans.MyIpaList; no valid constructor > at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:428) > at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:268) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1029) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) > at java.util.ArrayList.writeObject(ArrayList.java:570) > at sun.reflect.GeneratedMethodAccessor326.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:890) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1333) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245) > at > java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) > at > org.apache.myfaces.application.jsp.JspStateManagerImpl.serializeView(JspStateManagerImpl.java:590) > at > org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedViewInServletSession(JspStateManagerImpl.java:493) > at > org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:332) > at org.apache.myfaces.taglib.core.ViewTag.doAfterBody(ViewTag.java:122) > at > org.apache.jsp.myIpaList_jsp._jspx_meth_f_view_0(org.apache.jsp.myIpaList_jsp:204) > at > org.apache.jsp.myIpaList_jsp._jspService(org.apache.jsp.myIpaList_jsp:124) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322) > at > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) > at > org.apache.jetspeed.dispatcher.JetspeedRequestDispatcher.include(JetspeedRequestDispatcher.java:65) > at > org.apache.myfaces.context.portlet.PortletExternalContextImpl.dispatch(PortletExternalContextImpl.java:164) > at > org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:195) > at > org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:367) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:322) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:297) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:379) > at > org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:265) > >-----Original Message----- >From: Dennis Byrne [mailto:[EMAIL PROTECTED] >Sent: Friday, April 21, 2006 12:23 PM >To: [email protected] >Subject: Re: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT > >I highly doubt it but I am a little curious here. Can you post a full stack >trace please. I want to see at which point in the lifecyle this is happening. > In the meantime, please check for more than one definition of the class >laying around. > >Is it only the one class ? > >Is this class under /WEB-INF/lib, or in a global dir? > >Dennis Byrne > >>-----Original Message----- >>From: Nagaraddi, Prashant [mailto:[EMAIL PROTECTED] >>Sent: Friday, April 21, 2006 03:09 PM >>To: [EMAIL PROTECTED] >>Subject: RE: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >> >>Hi Dennis, >> >>Actually, I had the same setup with the 1.1.1 version and I didn't have the >>serialize/deserialize problems that I am now facing. I am using the the core >>1.1.3 and tomahawk 1.1.3-SNAPSHOP jars. Could it be that there is still an >>issue with the core? >> >>-Prashant. >> >>-----Original Message----- >>From: Dennis Byrne [mailto:[EMAIL PROTECTED] >>Sent: Friday, April 21, 2006 11:49 AM >>To: MyFaces Discussion >>Subject: Re: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >> >>Well, then you either have a serial version mismatch or there are unknown >>data types in the class. There was a bug in core related to this once but it >>was introduced after 1.1.1 and before 1.1.2 ( not in a release ). >> >>Dennis Byrne >> >>>-----Original Message----- >>>From: Nagaraddi, Prashant [mailto:[EMAIL PROTECTED] >>>Sent: Friday, April 21, 2006 02:38 PM >>>To: 'MyFaces Discussion' >>>Subject: RE: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >>> >>>Yes, I have already defined a default no-arg constructor for the MyIpaList. >>>I still get this error. >>> >>>-----Original Message----- >>>From: Dennis Byrne [mailto:[EMAIL PROTECTED] >>>Sent: Friday, April 21, 2006 11:23 AM >>>To: MyFaces Discussion >>>Subject: Re: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >>> >>>Try giving MyIpaList must have a default no-arg constructor. >>> >>>Dennis Byrne >>> >>>>-----Original Message----- >>>>From: Nagaraddi, Prashant [mailto:[EMAIL PROTECTED] >>>>Sent: Friday, April 21, 2006 02:19 PM >>>>To: 'MyFaces Discussion' >>>>Subject: RE: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >>>> >>>>Hello Mike, >>>> >>>>Thanks for that suggestion. Setting the configuration to use not check for >>>>extension filters gets rid of the error. However, I now face the following >>>>problem with serialization with a backing bean (I have <t:saveState> set >>>>for the bean in the JSP). The class in question has a default constructor >>>>defined taking no parameters. >>>> >>>>ERROR JspStateManagerImpl - Exiting deserializeView - Could not >>>>deserialize state: >>>>amazon.merchants.ipa.workflow.backingbeans.MyIpaList; no valid >>>>constructor >>>>java.io.InvalidClassException: >>>>amazon.merchants.ipa.workflow.backingbeans.MyIpaList; no valid constructor >>>> at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:428) >>>> at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:268) >>>> at >>>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1029) >>>> at >>>> java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245) >>>> at >>>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069) >>>> at >>>> java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1245) >>>> at >>>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1069) >>>> at >>>> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) >>>> at java.util.ArrayList.writeObject(ArrayList.java:570) >>>> at sun.reflect.GeneratedMethodAccessor326.invoke(Unknown Source) >>>> ... >>>> >>>>Any ideas as to why this happens? >>>> >>>>-Prashant. >>>> >>>>-----Original Message----- >>>>From: Mike Kienenberger [mailto:[EMAIL PROTECTED] >>>>Sent: Thursday, April 20, 2006 4:29 PM >>>>To: MyFaces Discussion >>>>Subject: Re: ExtensionsFilter error with Tomahawk-1.1.2-SNAPSHOT >>>> >>>>On 4/20/06, Nagaraddi, Prashant <[EMAIL PROTECTED]> wrote: >>>>> I am invoking a JSF page >>>>> via a Jetspeed 1.6 portlet >>>>>I get the >>>>> following error upon startup: >>>>> >>>>> java.lang.IllegalStateException: ExtensionsFilter not correctly >>>>> configured. >>>> >>>>Well, the base problem is that servlet filters don't work with portlets. >>>> >>>>Perhaps Mario's latest extension filter check is being too rigorous about >>>>requiring it. >>>> >>>>You might try setting this parameter and see if it gets you past the error, >>>>but some tomahawk functionality is not possible from a portlet. >>>> >>>> <context-param> >>>> <param-name>org.apache.myfaces.CHECK_EXTENSIONS_FILTER</param-name> >>>> <param-value>false</param-value> >>>> </context-param> >>>> >>> >>> >> >> > >
