•10 Tips for Killer Website Design
•7 Sure shots ways to improve your website
•Attracting Visitors and Improving Your Search Results
•Chasing the Search Engines Algorithms
•Crash Course in Getting a 1 Google Ranking
•Design Your Site for Traffic in 2005
•Designing A Website That Sells
•Googles Good Writing Content Filter
•How to Write Effective Web Copy
•How to Write Title Tags for Your Web Pages
•JSP Scripting Elements and Variables
•Java Brewing A Tutorial
•Java How to Send Email in Java
•Java Intro to JSP
•Java JSP Browser Detection
•Java JSP Syntax
•Java JSP versus ASP
•Java MySQL Database Connection
•Java Programming Language
•Java Virtual Machine
•Make Money Fast With Google Adwords
•Make Money On The Internet What Is Your Niche
•Make Money Quick With Google Adsense
•Ranked 1 at Google for Invisible Entrepreneurs But No Traffic
•Ruby Basic Input Output
•Ruby Classes Objects and Variables
•Ruby Containers Blocks and Iterators
•Ruby and the Web
•SEO One Way Web Links 5 Strategies
•SEO Success Step Two - Attracting Search Engine Attention
•The 10 Best Resources for CSS
•The 3 Best Website Traffic Sources
•The 5 Biggest Mistakes Almost All Web Designers Make
•The Click Fraud Problem
•The Five Ways You Should Be Using Keywords
•The Three Principles Of Image Optimization
•Top 5 Secrets to Making Money with Adsense
•True Paid Inclusion Programs are a Thing of the Past
•Understanding Web Logs And Why it Matters
Web Hosting Tips for Webmasters -
Java Server Pages (JSP)"
Java Server Pages (JSP)
JSP or JavaServer Pages, known to some as the Java Scripting Preprocessor, is a Java technology that allows developers to dynamically generate HTML, XML or some other type of web page. The technology allows Java code and certain pre-defined actions to be embedded into static content.
The JSP syntax adds additional XML tags, called JSP actions, to be used to invoke built-in functionality. Additionally, the technology allows for the creation of JSP tag libraries that act as extensions to the standard HTML or XML tags. Tag libraries provide a platform independent way of extending the capabilities of a web server.
JSPs are compiled into Servlets by a JSP compiler. A JSP compiler may generate a servlet in Java code that is then compiled by the Java compiler, or it may generate byte code for the servlet directly. In either case, it is helpful to understand how the JSP compiler transforms the page into a Java servlet. For an example, see the following input, and its resulting generated Java servlet.
JSP and Servlets
Architecturally speaking, you can view JSP as a high-level abstraction of servlets that is implemented as an extension of the Servlet 2.1 API.
A JavaServer Page may be broken down into the following pieces:
- static data such as HTML
- JSP directives such as the include directive
- JSP scripting elements and variables
- JSP actions
- custom tags
Static data is written out to the HTTP response exactly as it appears in the input file. Thus a valid JSP input would be a normal HTML page with no embedded java or actions. In that case, the same data would be sent in the response each and every time by the web server. Of course, the point of JSP is to allow dynamic data to be inserted into the static content.
JSP directives control how the JSP compiler generates the servlet. The following directives are available:
- include – The include directive informs the JSP compiler to include a complete file into the current file. It is as if the contents of the included file were pasted directly into the original file. This functionality is similar to the one provided by the C preprocessor.
<%@ include file="somefile.ext" %>
- page – There are several options to the page directive.
- import results in a java import statement being inserted into the resulting file
- contentType specifies the content that is generated. This should be used if HTML is not used or if the character set is not the default character set.
- errorPage indicates the page that will be shown if an exception occurs while processing the HTTP request.
- isErrorPage if set to true, it indicates that this is the error page.
- isThreadSafe indicates if the resulting servlet is thread safe.
- <%@ page import="java.util.*" %> //example import
- <%@ page contentType="text/html" %> //example contentType
- <%@ page isErrorPage=false %> //example for non error page
- <%@ page isThreadSafe=true %> //example for a thread safe JSP
Note: Only the "import" page directive can be used multiple times in the same JSP.