com.ail.core.ui
Class CarFileDownloadServlet

java.lang.Object
  javax.servlet.GenericServlet
      javax.servlet.http.HttpServlet
          com.ail.core.ui.CarFileDownloadServlet

All Implemented Interfaces:

java.io.Serializable, javax.servlet.Servlet, javax.servlet.ServletConfig

public class CarFileDownloadServlet
extends javax.servlet.http.HttpServlet

Servlet used by the configure system to download CAR (configuration archive) files.

See Also:

Serialized Form

Constructor Summary

CarFileDownloadServlet()

Method Summary

void	doGet(javax.servlet.http.HttpServletRequest request, javax.servlet.http.HttpServletResponse response) This servlet expects to recieve one parameter: carFile, which defines the absolute path to the file to be downloaded.

Methods inherited from class javax.servlet.http.HttpServlet

service

Methods inherited from class javax.servlet.GenericServlet

destroy, getInitParameter, getInitParameterNames, getServletConfig, getServletContext, getServletInfo, getServletName, init, init, log, log

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CarFileDownloadServlet

public CarFileDownloadServlet()

Method Detail

doGet

public void doGet(javax.servlet.http.HttpServletRequest request,
                  javax.servlet.http.HttpServletResponse response)
           throws javax.servlet.ServletException,
                  java.io.IOException

This servlet expects to recieve one parameter: carFile, which defines the absolute path to the file to be downloaded.
TODO: Performing the download via an intermediate file is less than optimal. There are two better alternatives, but nither proved reliable/possible:

• The controller (ConfigureManager) could directly write the config's byte[] into the response stream. However, the ConfigureManager is invoked from a portal which (rightly, by the portal spec) doesn't provide direct access to the response. So no go there.
• The controller could write the content into the session, and this servlet could pick it up and write it to the ServletResponse. This worked, but only for about 50% of requests - the other 50% didn't recieve the same session object, and hence didn't see the content. Bummer.

The second option is probably workable with more effort, but the intermediate file is simple, quick, and reliable, so we can live with it for now.

Overrides:

doGet in class javax.servlet.http.HttpServlet

Throws:

javax.servlet.ServletException

java.io.IOException