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> >
