Uh oh, sorry. It was my fault. getFile() in my backing had a return
type of String (copy&paste...). But the resulting exception was
really irritating. 

Regards & thanks
Helmut


>If the value is a valueBinding only the String #{xxxs.d} is serialized.
>Please try it with a managed bean that contains only the file nothing else.
>
>H. Swaczinna wrote:
>> Hello Bernd,
>> 
>> there was of cource a value binding. I stripped the example to the
>> bones, to see if it works eventually.
>> 
>> I learned meanwhile why there's the serialization. It's for the state
>> saving between request. But the question remains, how can state saving
>> ever work, when there's a class, which is not serializable 
>(DeferredFileOutputStream)?
>> 
>> Regards
>> Helmut
>> 
>> 
>>> Hello Helmut,
>>>
>>> oh tc:file without a valueBinding.
>>> Please add a valueBinding to tc:file.
>>> I should declare the property value required and it should be a 
>valueBinding
>>>
>>> Please consult the JSF Spec why stateSaving is required.
>>>
>>> Regards
>>>
>>> Bernd
>>>
>>> H. Swaczinna wrote:
>>>> Hello Bernd,
>>>>
>>>> there isn't any field in the bean. The exceptions occurs even there's
>>>> any bean at all. Example:
>>>>
>>>> <f:view>
>>>>   <tc:page label="Test" width="200px" height="100px">
>>>>     <tc:file/>
>>>>     <tc:button label="Submit"/>
>>>>   </tc:page>
>>>> </f:view>
>>>>
>>>> The problem is, that JSF tries to serialize the view. This can't work,
>>>> because the fileItem isn't serializable. The question is, why should
>>>> the view be serialized? Is this a problem with Tomcat (5.5.15)? I
>>>> use the standard configuaration.
>>>>
>>>> Regards
>>>> Helmut
>>>>
>>>>> Hello Helmut,
>>>>>
>>>>> I didn't know your managed bean. Can you declare the field in the 
>>>>> managed bean transient. Maybe the managed bean is a tabChangedListener?
>>>>>
>>>>> Regards
>>>>>
>>>>> Bernd
>>>>>
>>>>> H. Swaczinna wrote:
>>>>>> What do you mean exactly with statesaving tags? Any JSF or Tabago with a 
>
>>>>> state 
>>>>>> attribute?
>>>>>>
>>>>>> Helmut
>>>>>>
>>>>>>          No, the question was for removing these tags
>>>>>>
>>>>>>
>>>>>> H. Swaczinna escribió:
>>>>>>
>>>>>>     Adding Serializable doesn't help.
>>>>>>     I don't know any savestate or keepalive tags.
>>>>>>
>>>>>>     Helmut
>>>>>>
>>>>>>          AnlagenController implements the Serializable Class??
>>>>>>
>>>>>>
>>>>>>     Is there any savestate or keepalive tag in your jsp?
>>>>>>
>>>>>>
>>>>>>     H. Swaczinna escribió:
>>>>>>
>>>>>>         Hi,
>>>>>>
>>>>>>         I want to do a file uplaod with Tobago, but I always get an 
>>>>> exception
>>>>>>         when submitting the page:
>>>>>>
>>>>>>         2007-01-23 15:40:44 http-8080-Processor23 ERROR - 
>>>>> org.apache.myfaces.application.jsp.JspStateManagerImpl:599 - Exiting s
>>>>>>         erializeView - Could not serialize state: 
>>>>> org.apache.commons.fileupload.DeferredFileOutputStream
>>>>>>         java.io.NotSerializableException: 
>>>>> org.apache.commons.fileupload.DeferredFileOutputStream
>>>>>>                 at 
>>>>> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
>>>>>>                 at 
>>> 
>java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375)
>>>>>>                 at 
>>>>> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347)
>>>>>>         ...
>>>>>>
>>>>>>         JSP:
>>>>>>
>>>>>>         <tc:file id="dateiname" value="#{anlagenController.file}"/>
>>>>>>
>>>>>>         AnlagenController.java:
>>>>>>
>>>>>>           public void setFile(FileItem file) {
>>>>>>             LOG.error("Setting fileItem " + file.getName());
>>>>>>             this.filename = file.getName();
>>>>>>           }
>>>>>>
>>>>>>         web.xml:
>>>>>>
>>>>>>           <filter>
>>>>>>             <filter-name>multipartFormdataFilter</filter-name>
>>>>>>             
>>> 
><filter-class>org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter</f
>
>>>
>>>>> ilter-class>
>>>>>>           </filter>
>>>>>>
>>>>>>         classpath:
>>>>>>
>>>>>>         tobago-fileupload-1.0.10-SNAPSHOT.jar
>>>>>>         commons-fileupload-1.0.jar
>>>>>>
>>>>>>
>>>>>>         I've no idea what's wrong or missing. And there's no 
>>> documentation,
>>>>>>         except the simple example in the source...
>>>>>>
>>>>>>         Regards
>>>>>>         Helmut
>>>>>>           
>>>>>>
>>>>>>
>>>>>>
>>>>>>     -- 
>>>>>>
>>>>>>      
>>>>>>
>>>>>>     *Carlos López Rodríguez*
>>>>>>     R&D Department
>>>>>>     [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>>>>>     Tel. +34 93 556 52 00
>>>>>>
>>>>>>     <http://www.infinity.es>
>>>>>>
>>>>>>     
>>>>> ________________________________________________________________________
>>>>>>     Disclaimer: The content of this message (and of all the files 
>>> attached) 
>>>>> is
>>>>>>     confidential, and is forwarded exclusively to the specified 
>addresses. 
>>>>> The
>>>>>>     message may contain privileged information and/or be legally 
>>> protected. 
>>>>> You
>>>>>>     can only reproduce or distribute this material if you are 
>>> specifically
>>>>>>     authorized to do so.
>>>>>>
>>>>>>     If you are not the intended recipient, any use, disclosure or 
>copying 
>>>>> of
>>>>>>     this e-mail (and any attachments) is unauthorized. If you have 
>>> received 
>>>>> this
>>>>>>     e-mail in error, please immediately delete it and any copies of it 
>>>from 
>>>>> your
>>>>>>     system and notify us via e-mail at [EMAIL PROTECTED]
>>>>>>     <mailto:[EMAIL PROTECTED]>. Thank you.
>>>>>>
>>>>>>     
>>>>> ________________________________________________________________________
>>>>>>
>>>>>> -- 
>>>>>>
>>>>>>  
>>>>>>
>>>>>> *Carlos López Rodríguez*
>>>>>> R&D Department
>>>>>> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>>>>> Tel. +34 93 556 52 00
>>>>>>
>>>>>> <http://www.infinity.es>
>>>>>>
>>>>>> 
>________________________________________________________________________
>>>>>>
>>>>>> Disclaimer: The content of this message (and of all the files attached) 
>is 
>>>>>> confidential, and is forwarded exclusively to the specified addresses. 
>The 
>>>>>> message may contain privileged information and/or be legally protected. 
>
>>> You 
>>>>> can 
>>>>>> only reproduce or distribute this material if you are specifically 
>>>>> authorized to 
>>>>>> do so.
>>>>>>
>>>>>> If you are not the intended recipient, any use, disclosure or copying of 
>
>>>>> this 
>>>>>> e-mail (and any attachments) is unauthorized. If you have received this 
>
>>>>> e-mail 
>>>>>> in error, please immediately delete it and any copies of it from your 
>>> system 
>>>>> and 
>>>>>> notify us via e-mail at [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>. 
>Thank 
>>>>> you.
>>>>>> 
>________________________________________________________________________
>>>>>>
>>

Reply via email to