Application

application

N/A

javax.servlet.ServletContext

Application(String name) ="Your Data"

setAttribute(String name,Object object)*

Set Application(String name) =Server.CreateObject(String name)

As Above

My_Variable = Application(String name)

getAttribute (String name)*

Set My_Object =Application(String name)

As Above

Contents.Remove(String name)

removeAttribute(String name)

Contents
    
Code Example:
<%
 Dim ls_write 
 For Each Key in Application.Contents
     ls_write = Key + " : "+ Application(Key)
 Next
%>

getAttributeNames()

This returns an enumeration of string objects containing the names of attributes stored in the application object.

N/A

getServerInfo()

N/A

getMajorVersion()
getMinorVersion()

N/A
See Response.AppendToLog(string)

log(String msg)

N/A

String= getMimeType(String file)

N/A
See ASP Server.MapPath(Path)

String =getRealPath(String virtualpath)

N/A

URL = getResource(String path)

ASP doesn't have a similar object.

config

N/A

javax.servlet.ServletConfig

N/A

getServletName

N/A

getServletContext()

N/A

getInitParameterNames()

N/A

getInitParameter(String name)

ASPError

exception

N/A

java.lang.Throwable

A new ASP 3.0 / IIS 5.0 object.
You call Server.GetLastError method to receive the ASPError object.

You only have access to this object if you declare your JSP page as an error page. To do this you use the declaration:
<%@ page isErrorPage="true" %>

Description ()

getMessage()

ASPDescription()

toString()

N/A

printStackTrace(out)

Line
Column

N/A

Response

out

N/A

javax.servlet.jsp.JspWriter

ASP uses the Response Object to perform most of these functions

Write variant

print(object or primitive data type)

BinaryWrite data

You need to access the Java OutputStream class and use its binary write methods.
Quick Example:

ServletOutputStream Output = response.getOutputStream();
Output.write(Btye[] buffer);

Clear

clearBuffer()

Flush

flush()

End

close()
This is different than end. It closes off the current output stream. The JSP page is still free to finish its processing.

ASP doesn't have an object like this one.

page

N/A

java.lang.Object

This object is rarely directly used, since when using Java as your scripting language, you already have access to the whole page object through the "this" keyword. This object is present for giving other scripting languages access to your JSP pages methods and attributes.

ASP doesn't have an object like this one.

pageContext

N/A

javax.servlet.jsp.PageContext

Request

request

N/A

Subclass of:
javax.servlet.ServletRequest
Usually:
javax.servlet.HttpServletRequest

  ClientCertificate(Key[Field])

N/A

  Cookies(cookie)[(key).attribute]

cookie[]=getCookies()

string = getParameter(Name)
Enum = getParameterNames()
string[]  = getParameterValues(name)

For example:
ls_form = request.getParameter("date");

  QueryString(element)[(index)|.Count]

getParameter(Name)
getQueryString() (entire query string)

  ServerVariables (server environment var)

For example:

ServerVariables (ALL_RAW) returns to you all the headers in raw format

getHeaderNames()
getHeader(name)
getHeaders(name)
getIntHeader(name)
getDateHeader(name)

Response

response

N/A

Subclass of: javax.servlet.ServletResponse
Usually:
javax.servlet.HttpServletResponse

 Buffer = True/False

By default, JSP buffers the first 8k of output. After this limit has been reached, it flushes the output. You use the page directive to change the buffer size and state. For example, to turn buffering off:

<%@ page  buffer= "none" %>

CacheControl =Private/Public

setHeader("Pragma","no-cache")
setHeader("Cache-Control","no-cache")

Cookies(cookie)[(key).attribute] = value 

addCookie(cookie)

AddHeader Name,Value

setHeader(Name,Value)

Redirect URL

sendRedirect(Absolute URL)

(see also encodeRedirectURL() if you are using URL rewriting as your session management.)

N/A
You can use VbScript to raise an error, but it isn't as clean.

sendError(int code,String msg)

N/A
Function of the server object.
See Server.URLencode.

encodeURL(name)

Note, if you are using URL rewriting as your session management, then this function also appends the session ID for this purpose.

ContentType = "MIME TYPE"

setContentType("MIME TYPE")

Server

JSP doesn't have a Server object. The functions found in the ASP server object are distributed across the other JSP implicit objects.

N/A

N/A

CreateObject(Object id)

Use standard Java syntax to create objects.

HTMLEncode(String)

N/A

MapPath( Path )

N/A
see JSP application.getRealPath(virtualpath)

URLEncode(String)

N/A
see JSP response.encodeURL(name)

(IIS 5.0 / ASP 3.0) Transfer

N/A
see file redirection

ScriptTimeout = Seconds

N/A
This is a feature that would be container specific in JSP. Currently Tomcat doesn't have a timeout feature.

Session

session

N/A

javax.servlet.http.HttpSession

ASP manages Session by using cookies only.

JSP has two methods of Session management.

1. Using cookies
2. URL rewriting

Abandon

invalidate()

Session (String name) ="Your Data"

setAttribute(String name,Object object)*

Set Session (String name) = Server.CreateObject(String name)

As Above

My_Variable = Session(String name)

getAttribute (String name)*

Set My_Object = Session(String name)

As Above

Contents.Remove(String name)

removeAttribute(String name)

Contents

getAttributeNames()

This returns an Enumeration of String objects containing the names of attributes stored in the application object.

SessionID

string =getId()

Timeout(Minutes)

setMaxInactiveInterval(int interval in seconds)

N/A

int =getMaxInactiveInterval()

LCID(Locale ID)

see Request Object getLocale

A Directive Command
<%@ EnableSessionState = False%>

A Directive Command
<%@ page session="false"%>

<% Your Server Side Script %>

<% Your Server Side Script %>

<%= Your_Variable %>

<%= Your_Variable %>

<% Your Function %>

<%!  Your Function %>

• A declaration is a complete logical unit of work.
• Declarations don't produce any results into the output buffer.
• Declarations are initialized when the JSP page is initialized.
• Code within declarations is made available to other declarations, expressions and scriptlets.
• Variables created within a declaration block become instance variables. Since JSP Containers tend to only make one instance of a page to share requests against, this can mean that all current instances of the JSP page have access to the same variable. In other words, if your page is currently being accessed at the same time by 10 users, those 10 users are sharing one variable. For all practical purposes you are creating a class variable. If you want to avoid this, you can create variables within your scriptlet block. Variables declared within a scriptlet block are local to that script block. You can also set
  <%@ page isThreadSafe="false" %> to get around this issue. However, using the isThreadSafe property has serious performance issues on high traffic sites. If you want to use your variable as a class variable we recommend that you declare it as such and don't count on this behavior as being the rule.
• You can also declare class variables and functions in a declaration block.

<%@ Your Directive %>

<%@ Your Directive %>

Example of setting the scripting language:
<%@ LANGUAGE="VBSCRIPT" %>

Please note many of the directives found in JSP are not directives in ASP. Rather you will find what you might think of a directive is actually a property of one of the ASP objects. Setting these properties will have global effects on the page.
For example to turn page buffering on you would write the following code:
<%response.buffer=true%>

• Directives are messages to the JSP container.
• Directives don't produce any results into the output buffer.
• Directives are processed when the JSP page is initialized.

N/A

<jsp:Action> or <yourtag:YourAction>

N/A

• These tags are case sensitive.
• There are a standard set of actions which must be supported by all containers. For example you will always be able to use the <jsp:forward> action.
• Attributes must be quoted (see example).
• Tags must have a closing delimiter.
• You can build new actions.
• You can extend existing actions.
• Actions can put data into the output buffer.
• Actions can access, modify and create objects on the current server page.

Example to access a JavaBean
<jsp:useBean id="myBean" class="beans.htmlBean" />

Note, when you hear the term tag library, it refers to a custom built collection of actions.

VbScript uses:

a single quote '
<% 'Your Comment %>

Java uses:
 // for a single line
 /* */ for multiple lines.
<%//my comment %> or
<% /* my
         comment */ %>

N/A

<!--#include file="Your File.asp" -->

<!--#include virtual ="/Your File.asp"-->

Usage Notes:

The keyword "Virtual" indicates you are using a full virtual path from a virtual directory in your Web site. When you use the keyword "File", you are using a relative path from the directory containing the document.

You can include a file using a directive:

<%@ include file="Your File" %>

 or  in tag format

<jsp:directive.include file="Your File" %>

• You can include HTML or additional ASP scripting elements.
• The files are combined into a single source code and then translated into a result.
• You cannot use scripting conditional logic to make the include statements conditional, since the include directive is preprocessed before scripting code executes to process the conditional.
• The files are combined into a single source code and then ASP logic is performed.

• The file can be passed as either a relative path or an absolute path.
• You can include HTML or additional JSP scripting elements.
• You cannot use scripting conditional logic to make the include statements conditional, since the include directive is preprocessed before scripting code executes to process the conditional.
• The files are combined into a single source code and then translated into a servlet.
• The JSP container will only recombine the include files and the main page when the main page has been modified. So if you change an include file but not the page that references it, no new servlet will be generated.
• The included page shares all local information and shares the same pageContext Object.
• Faster than using the jsp:include action.This is due to the static include being preprocessed during page translation and compiled into a servlet.

IIS 5.0 / ASP 3.0 Introduces Server.Execute.

Usage Notes:
This function will let you execute an ASP page from within another ASP page

<jsp:include page="Your File" flush="true">

If you desire to pass additional information to the included page use the following format:

<jsp:include page="Your File" flush="true">

      <jsp: param name = "Name" value ="Data" />

</ jsp:include>

Usage Notes:
You can pass as many parameters as you need using this method.

The flush property is used to tell the page to flush the current output buffer of the current page before the action of the including the new file. Currently you can only set this property to true. Since the previous page's buffer has been flushed and you cannot forward to another page.

• You may include a text file(HTML), a CGI script, a servlet or another JSP page. You can include dynamic real time content.
• The included page receives a new pageContext object.
• The include page shares the request and session objects as the original page.
• You can dynamically pass additional information to the include page by using parameters.
• The processing of the included file happens during the request of the current page this means:
  a) you can dynamically change what your include processes.
  b) your latest include file will always be processed.
  c) you can not only include contents of a file but you can also include dynamic output.
• Restricts one from setting response headers and the response code.

response.redirect("to_File.asp")

response.sendRedirect(ls_Absolute_Url)

• The file may be passed as either a relative path or an absolute path.
• Once the header has been sent down to the user, you cannot redirect to a different page.
• This command has the server send a HTTP response to the browser asking it to load a new URL

• This only works with an absolute URL. (Major Bummer).
• You can only redirect to a new page provided no output of the original page has been sent to the browser.
• I have read that sendRedirect actually, creates a new thread for the new pages redirection, while the old thread and page keeps executing until it finishes at end of the original page. I haven't seen this behavior yet and don't know if it is part of the JSP specs or a by product of a JSP containers implementation.

In IIS 5.0 / ASP 3.0
You can use Server.Transfer.

Usage Notes:
Server.Transfer ends execution of the current asp page without clearing the output. The new page has access to same set objects (Application, Request, Response, Server, Session) as the starting file. To the browser it will appear you have the originally requested page not the page to which you are transferred.

Using an action:

<jsp:forward page="home/Default.jsp" / >

OR with parameters

<jsp:forward page="home/Default.jsp" >
       <jsp:param name="source" value="entry"/>
</jsp:forward>

Usage Notes:
You may pass as many parameters as you need using this method by using the param tag.

The forward action ends execution of the current JSP page and removes any existing buffered output. The new page has access to following objects (Application, Request, Session) as the starting file. A new pageContext object is generated for the page. To the browser it will appear you have the originally requested page not the page to which you are transferred.

• You can forward to a text file(HTML), a CGI script, a servlet or another JSP page.
• You can only forward to a new page provided no output of the original page has been sent to the browser.