SnuggleTeX 1.3.0 · uk.ac.ed.ph.snuggletex.webapp.UpConversionExampleFragmentServlet

Field Summary

Modifier and Type	Field and Description
private static final String	DEFAULT_UPCONVERSION_OPTIONS Default assumptions to use here
private static final String	DISPLAY_XSLT_LOCATION Location of XSLT controlling page layout
private static Logger	logger Logger so that we can log what users are trying out to allow us to improve things
private static final long	serialVersionUID Hides uk.ac.ed.ph.snuggletex.webapp.BaseServlet.serialVersionUID.

Access	Constructor and Description
public	UpConversionExampleFragmentServlet()

Method Summary

Modifier and Type	Method and Description
protected void	doGet(HttpServletRequest request, HttpServletResponse response) Overrides javax.servlet.http.HttpServlet.doGet. Called by the server (via the `service` method) to allow a servlet to handle a GET request.
private void	doRequest(HttpServletRequest request, HttpServletResponse response)

Inherited from uk.ac.ed.ph.snuggletex.webapp.BaseServlet:: chooseBestBaseWebPageOutputOptions chooseBestWebPageType createMathMLSourceSerializationOptions createSnuggleEngine ensureGetContextInitParam ensureReadResource extractMathMLElement getStylesheet getStylesheetCache getStylesheetManager isInternetExplorer isMathMLCapable

Field Detail

DEFAULT_UPCONVERSION_OPTIONS	back to summary
private static final String DEFAULT_UPCONVERSION_OPTIONS Default assumptions to use here

DISPLAY_XSLT_LOCATION	back to summary
private static final String DISPLAY_XSLT_LOCATION Location of XSLT controlling page layout

logger	back to summary
private static Logger logger Logger so that we can log what users are trying out to allow us to improve things

serialVersionUID	back to summary
private static final long serialVersionUID Hides uk.ac.ed.ph.snuggletex.webapp.BaseServlet.serialVersionUID.

Constructor Detail

UpConversionExampleFragmentServlet	back to summary
public UpConversionExampleFragmentServlet()

Method Detail

doGet back to summary

doGet	back to summary
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException Overrides javax.servlet.http.HttpServlet.doGet. Doc from javax.servlet.http.HttpServlet.doGet. Called by the server (via the `service` method) to allow a servlet to handle a GET request. Overriding this method to support a GET request also automatically supports an HTTP HEAD request. A HEAD request is a GET request that returns no body in the response, only the request header fields. When overriding this method, read the request data, write the response headers, get the response's writer or output stream object, and finally, write the response data. It's best to include content type and encoding. When using a `PrintWriter` object to return the response, set the content type before accessing the `PrintWriter` object. The servlet container must write the headers before committing the response, because in HTTP the headers must be sent before the response body. Where possible, set the Content-Length header (with the `javax.servlet.ServletResponse#setContentLength` method), to allow the servlet container to use a persistent connection to return its response to the client, improving performance. The content length is automatically set if the entire response fits inside the response buffer. When using HTTP 1.1 chunked encoding (which means that the response has a Transfer-Encoding header), do not set the Content-Length header. The GET method should be safe, that is, without any side effects for which users are held responsible. For example, most form queries have no side effects. If a client request is intended to change stored data, the request should use some other HTTP method. The GET method should also be idempotent, meaning that it can be safely repeated. Sometimes making a method safe also makes it idempotent. For example, repeating queries is both safe and idempotent, but buying a product online or modifying data is neither safe nor idempotent. If the request is incorrectly formatted, `doGet` returns an HTTP "Bad Request" message. Annotations @Override Exceptions ServletException: if the request for the GET could not be handled IOException: if an input or output error is detected when the servlet handles the GET request

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException

Overrides javax.servlet.http.HttpServlet.doGet.

Doc from javax.servlet.http.HttpServlet.doGet.

Called by the server (via the service method) to allow a servlet to handle a GET request.

Overriding this method to support a GET request also automatically supports an HTTP HEAD request. A HEAD request is a GET request that returns no body in the response, only the request header fields.

When overriding this method, read the request data, write the response headers, get the response's writer or output stream object, and finally, write the response data. It's best to include content type and encoding. When using a PrintWriter object to return the response, set the content type before accessing the PrintWriter object.

The servlet container must write the headers before committing the response, because in HTTP the headers must be sent before the response body.

Where possible, set the Content-Length header (with the javax.servlet.ServletResponse#setContentLength method), to allow the servlet container to use a persistent connection to return its response to the client, improving performance. The content length is automatically set if the entire response fits inside the response buffer.

When using HTTP 1.1 chunked encoding (which means that the response has a Transfer-Encoding header), do not set the Content-Length header.

The GET method should be safe, that is, without any side effects for which users are held responsible. For example, most form queries have no side effects. If a client request is intended to change stored data, the request should use some other HTTP method.

The GET method should also be idempotent, meaning that it can be safely repeated. Sometimes making a method safe also makes it idempotent. For example, repeating queries is both safe and idempotent, but buying a product online or modifying data is neither safe nor idempotent.

If the request is incorrectly formatted, doGet returns an HTTP "Bad Request" message.

Annotations

@Override

Exceptions

ServletException:: if the request for the GET could not be handled
IOException:: if an input or output error is detected when the servlet handles the GET request

doRequest	back to summary
private void doRequest(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException

public final Class UpConversionExampleFragmentServlet

Field Summary

Constructor Summary

Method Summary

Field Detail

Constructor Detail

Method Detail