“In struts 2.0 you can return Action.NONE in execute method and dont specify anything in struts.xml action specification. Use the output stream as like in struts. “

This is going to be an issue with sending any file over HTTP, because you can’t send both text (a message) and a file for display in a browser at the same time.

You could try sending a http redirect header along with the file, but I’m not sure exactly how to do this.

In struts 1, is there any way to show errors or messages after file output.

I need to export a file of ms-excel type and display a message using saveErrors(req,err) or saveMessages(req,msg) methods.

But after file export. i got a exception as,

SEVERE: Servlet.service() for servlet ActionServlet threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response

and the page is not forwarding. even the data in the forms are not reset. (i called actionForm.reset() method.)

any clues.
thanks.

File pdfFile = new File(pdfFileName);
response.setContentType(BIRTSchedulerConstants.CONTENT_TYPE);
response.setContentLength((int) pdfFile.length());

response.setHeader(“Content-Disposition”, “attachment; filename=\”" + pdfFile.getName() + “\”");

response.setHeader(BIRTSchedulerConstants.CACHE_CONTROL, BIRTSchedulerConstants.NO_CACHE);
response.flushBuffer();
OutputStream outStream = response.getOutputStream();
byte[] buf = new byte[(int) pdfFile.length()];
FileInputStream inStream = new FileInputStream(pdfFile);
int sizeRead = 0;
while ((sizeRead = inStream.read(buf, 0, buf.length)) > 0) {
outStream.write(buf, 0, sizeRead);
}
inStream.close();
outStream.flush();

Note: In struts action, use the mapping.findforward(null). becoz flush() method will submit the data to response stream. so if u redirect to another page then u will get response.getOutputStream() been already called error.

I did the file reading and wrote it to the Outputstream and then retun null instead of any action. This solved my issue and everything is fine.

It is just that we open a ouput stream in the action and when we forward to any jsp, the container tries to open an output stream to write the JSP contents.

Non-working jsp jsp:

<%@ page
…
%><jsp:useBean
id=”actionForm”
scope=”request”
type=”mypackage.MyActionForm”>
</jsp:useBean><% /** Java code **/ %>

Working jsp:

<%@ page
…
%><jsp:useBean
id=”actionForm”
scope=”request”
type=”mypackage.MyActionForm”
></jsp:useBean><% /** Java code **/ %>

Everything worked fine in WAS4, but not now in WAS6. The binary data is generated and displayed on screen, but it is followed by ugly
stack traces on the server console: “OutputStream already obtained”.

But by inspecting the stack trace, I realised that the exception was *not* thrown when my code “response.getOutputstream” was executed.
Instead, the exception was thrown after all the code in the JSP had finished executing, which explains why I first got the file and then
was followed by the ugly stack trace.

I also found the cause. WAS has a feature called “keepgenerated” which, if set to true, keeps the java code that is generated from the
JSP. By inspecting the generated java code I discovered that WAS6 causes a \r\n to be written to the implicit variable “out” (of type
JSPWriter):

<jsp:useBean
id=”actionForm”
scope=”request”
type=”mypackage.MyActionForm”>
</jsp:useBean>

The exception was thrown when WAS tried to flush “out” (containing the \r\n), *after* the binary data had been sent to the client.

It didn’t help to write like this either:

&lt%@ page
…
%><jsp:useBean
…
</jsp:useBean><% /** Java code **/ %>

The solution was to replace the useBean tag with java code:

<%@ page
…
%><%

mypackage.MyActionForm actionForm = null;
actionForm = (mypackage.MyActionForm) request.getAttribute(“actionForm”);

/** Java code **/ %>