OutputStream instead of out

[Pradeep bhatt]

Hi,
Is anything wrong in using getOutputStream rather than using PrintWriter in JSP?

[David O'Meara]

Shouldn't be, I've used it on occasion. There are a few dangers though. You have to make sure no character data is printed, including white-space. You also lose your error page, since it makes use of 'out' and you can't have both.
With white-space, you have to join your scriptlets and other JSP tags together so there is no data leaking through. You also have to make sure there is no carriage return at the end. To link tags together, you have to do this:

<%@page import="..."%><%
//the previous line makes sure a carriage return doesn't get printed
%>

and not this:

<%@page import="..."%>
<%
//the carriage return is outside the scriptlets and counts as character data!
%>

I'm not aware of any vendor specific behaviour here.
Dave

[Pradeep bhatt]

David,
Thanks.
Can you tell me why I should not have any space between page tag and the scriptlet.
I am doing the following

 OutputStream os= response.getOutputStrem();
os.write(...);
os.close();
 

So, You have changed your signature.

[William Brogden]

JSP have the built in assumption that you will be wanting to output a mix of the text that appears between the JSP tags and the output of the Java methods created by the tags. All output is assumed to be characters and will be subject to unicode conversion.
Use a servlet to output binary data such as images, etc.
Bill

[Pradeep bhatt]

Bill,
Well I am forced to use a JSP. No choice!


I am outputing HTML code from OutputStream.