Rob,
Which servlet engine are you using?
Usually this problem occurs because of either the flushing problem of
Printwriter or breaking of ServletOutputStream.
In WebSphere this happens when running out of process, also any JSP more
than 16K cannot be rendered properly. I have experienced same problem with
JRun too. Here is the fix.
Create your own buffer like
ByteArrayOutputStream buf = new ByteArrayOutputStream(81920);
PrintWriter out = new PrintWriter(buf); //Wrap it around a PrintWriter
out.println("Write your Data here"); //Print your Data
.
.
out.flush(); //Flush the Buffer
buf.writeTo(ServletOutputStream); // Write the buffer on to the
ServletOutputStream
If you are using WAS 2.0 and want to be running out of process, there is a
fix for this from IBM. Please install this fix when deploying the software
on 2.0 - Go to
http://www.software.ibm.com/webservers/appserv/download.html#ntse and
install the fix.
Or else just go in process after changing your code as mentioned above. In
JRun also this wor around seems to work.
Thanks
Rajan
> -----Original Message-----
> From: Rob Jago [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, April 01, 1999 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: IE problems with large table displays
>
> Hello
>
> I am wondering if anyone has encountered the following problem and
> if so, how did you work around it.
>
> I am creating StringBuffer that contains a large table (about 140 rows
> with
> 4 columns per row) (roughly 30000 characters in total)
>
> I checked the contents of this html table (contained in the StringBuffer)
> before sending it down and all the appropriate html tags are there. But
> when this same table (StringBuffer and all) is sent back to Internet
> Explorer I get strange results.. often the HTML table is not formatted
> properly with some rows not being displayed and others concatenated
> together
> (causing the display to a 8 column table as opposed toa 4 column table)
>
> I am getting the same errors whether sending the StringBuffer via
> PrintWriter or via ServletOutputStream or via sending the String to a
> JSP.
>
>
> I am quite sure I will be redoing pieces of the code but I am
> wondering if there is a way to avoid this (ex. setting the size of the
> file
> size to send back as in the setHeader method call)
>
> thanks for any input
>
> Rob Jago
> Programmer Analyst
> Ottawa
>
> __________________________________________________________________________
> _
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
