Re: AW: AW: AW: java.io.IOException: Stream closed

2008-12-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan, Schuster Stefan wrote: As far as I can tell, the XML-Beans generated code works well - even if The stream is closed after reading, this should be no problem as the next request will submit a new stream, right? Yes, your servlet can close

AW: AW: AW: java.io.IOException: Stream closed

2008-12-11 Thread Schuster Stefan
PROTECTED] Gesendet: Freitag, 5. Dezember 2008 17:43 An: Tomcat Users List Betreff: Re: AW: AW: java.io.IOException: Stream closed -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan, Schuster Stefan wrote: The code reading the stream is generated by XMLBeans. Is there something that I should

AW: AW: java.io.IOException: Stream closed

2008-12-05 Thread Schuster Stefan
(); return null; } } } -Ursprüngliche Nachricht- Von: Christopher Schultz [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 4. Dezember 2008 23:22 An: Tomcat Users List Betreff: Re: AW: java.io.IOException: Stream closed -BEGIN PGP SIGNED

Re: AW: AW: java.io.IOException: Stream closed

2008-12-05 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan, Schuster Stefan wrote: The code reading the stream is generated by XMLBeans. Is there something that I should not do with the stream? For example closing it or something like that? You shouldn't have to do anything like that. ERROR

AW: java.io.IOException: Stream closed

2008-12-04 Thread Schuster Stefan
Hi everybody, I still have the problem mentioned below. I just don't have any idea where to start with problem solving? Can it be a problem in Tomcat? I guess not as this is a very simple use-case (read the stream in the servlet) and it would have probably come up ealier... Any Ideas? Please?

Re: AW: java.io.IOException: Stream closed

2008-12-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stafan, Schuster Stefan wrote: I still have the problem mentioned below. I just don't have any idea where to start with problem solving? Can it be a problem in Tomcat? I guess not as this is a very simple use-case (read the stream in the servlet)