| |
|
JSP Hosting
(Java
Server Pages)
JSP
versions supported
We use
the
Resin JSP engine to power our
Website hosting services.
-
Resin Engine
version 2.1.10
-
JSP version 1.2
-
Java servlets
written to the 2.3 version of the JSP Servlet specification
-
The JSP Engine we
use is Resin
-
JDK version 1.4.2
compliant VM
What is JSP and what
are Javabeans and EJB components?
[From:
JSP 101: Introduction to JavaServer Pages
by JJ Kuslich] JSP Basics
Java Server Pages (JSP) technology allows the combination of regular,
static HTML and XML and Java code to produce dynamic, portable,
scalable and easily maintained pages.
JSP technology acts as a top layer above Java servlets on the
servlet engine. In this way, developers can combine HTML code with
server-side scripting to create dynamic pages.
Incorporating Components
JSP is based on components. It uses JavaBeans and Enterprise
JavaBeans (EJB) components which hold the business logic for an
application, and it composes tags and a scripting platform for
presenting the content generated and returned by the beans into HTML
pages. The components structure means that non-Java developers can use
JSP to manipulate beans that developers have built. On the other hand,
Java developers can use these beans and Java in JSP pages for more
advanced productions based on the beans.
Request Model
The following model is based upon a diagram from the following page
-
http://developer.netscape.com/viewsource/kuslich_jsp/
kuslich_jsp.html.
It follows the path of a JSP request. A user requests a page
through a browser. The browser sends out the request for a JSP page.
The request goes via a web server which contains a JSP engine (for
example, Resin). Resin compiles the servlet. The servlet goes through
the Beans, to a database to retrieve the relevant information. Once it
collects the information from the database, it travels back to the web
server, where this information is collated with the servlet
information into the correct format and is sent back to the browser as
a JSP page.
BROWSER - INTERNET - JSP PAGE - BEANS - DATABASE
What is really happening in this process? A user calls a JSP page
through their browser, so Resin (for instance) located on the web
server, converts JavaScript, JSP tags, and HTML into segments of Java
code, which the engine then consequentially arranges into a core Java
servlet. This core servlet is therefore pre-assembled and works
'behind the scenes'. It is called every time that particular page is
requested by a user, saving valuable recompiling time. The next time a
user calls that page from their browser, because the JSP code has
already been compiled, it does not have to convert the JavaScript,
HTML, etc each time. That is, the servlet engine needs only to produce
that servlet once, or after the last code change was updated. In this
example, the JSP Engine,
Resin acts to eliminate duplicate effort.
Benefits of our
JSP Hosting
-
Resin has
considerably faster response times to other JSP Engines
-
Resin mod_perl,
mod_php, and other servlet engines in performance benchmarks
-
Resin
autocompiles Java servlets, classes, and beans-not just JSP, so
instead of setting up a make system, you can simply change the code
and click on your browser for an instant test
-
Seriftm compiles
XML to JSP, chopping up the source code and feeding it to JSP for
efficient processing, giving you the flexibility of Stylesheets and
the performance of JSP
-
Resin-JavaScript
compiles JavaScript directly to Java byte codes
-
Resin's caching
saves pages so they don't have to be reassembled repeatedly from
scratch, cutting down on response time and alleviating database
bottlenecks
-
Resin's
distributed session load balancing lets sites process dynamic sites
quickly. Servlets and JSP pages can take time: they may need to
query databases, read files, and calculate. Multiple servers (real
or virtual) balanced by Resin support several Java processes
simultaneously and cut down on response time.
PERL
|
FRONTPAGE
|
ASP
|
JSP
|
PHP
|
MYSQL
|
POSTGRE SQL
|
PYTHON
|
ZOPE
|
|
