[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leonardo Uribe resolved TOMAHAWK-1208.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.9-SNAPSHOT
         Assignee: Leonardo Uribe

Added test for object serialization and added inner classes that implements 
Serializable interface

> NotSerializableException for 
> org.apache.myfaces.custom.fileupload.UploadedFileDefaultMemoryImpl$1
> -------------------------------------------------------------------------------------------------
>
>                 Key: TOMAHAWK-1208
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1208
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: File Upload
>    Affects Versions: 1.1.7-SNAPSHOT
>         Environment: Apache Tomcat 5.5.23, Tomahawk 1.1.7 Snapshot (8. 
> January 2008), myfaces 1.1.6, tiles 2.0.5
>            Reporter: Erol Koc
>            Assignee: Leonardo Uribe
>             Fix For: 1.1.9-SNAPSHOT
>
>
> Since we decided to use Tiles 2 in our project, we had to upgrade from 
> tomahawk 1.1.6 to the next available version (currently tomahawk 1.1.7 
> snapshot) to be able to use the JspTilesTwoViewHandler. However, with this 
> upgrade, we now get the following exception on pages using the 
> t:inputFileUpload tag:
> ERROR 03/Mar/08:14:48:08: Exiting serializeView - Could not serialize state: 
> org.apache.myfaces.custom.fileupload.UploadedFileDefaultMemoryImpl$1 
> <org.apache.myfaces.application.jsp.JspStateManagerImpl:520>
> java.io.NotSerializableException: 
> org.apache.myfaces.custom.fileupload.UploadedFileDefaultMemoryImpl$1
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>         at 
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>         at 
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>         at 
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251)
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251)
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251)
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
>         at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251)
>         at 
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
>         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
>         at java.util.ArrayList.writeObject(ArrayList.java:569)
>         at sun.reflect.GeneratedMethodAccessor268.invoke(Unknown Source)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> To be more precise: the exception occurrs on pages containing a sortable 
> table and the and at least one t:inputFileUpload (both in the same form). 
> Whenever the table is sorted, the exception is thrown. Unfortunately, all 
> other command links do not work for the next click!
> The $1 at the end of UploadedFileDefaultMemoryImpl$1 indicates that there is 
> an inner class which does not implement the Serializable interface.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to