|
|
![]() |
|
|
1. IIS and Tomcat - how to configure to work together
|
|
By: Emiley J. : 2009-09-01
|
|
Description: This tutorial explains how to configure your IIS (in this example IIS 5.0, since I have not upgraded yet) and Tomcat 4.1 xxx version (again since I have not upgraded yet). But the concept should be the same. So if you want to host some JSP files or servlets on your Tomcat which is installed in port 8080 and your IIS is installed on the same machine at port 80 and you want to direct all JSP files also to port 80 so that IIS can forward these queries to tomcat internally and respond. So the user does not have to type 8080 on the url. Well if you want to do that then these are the steps. |
|
Read the full article
|
|
2. Drawbacks of the JSP Model 1 Architecture
|
|
By: Barbara : 2008-12-09
|
|
Description: The Model 1 architecture has one thing going for it: simplicity. If your project is small, simple, and self-contained, it's the quickest way to get up and running. But the previous example, although by no means large or complicated, already illustrates a number of the disadvantages of Model 1 architecture: |
|
Read the full article
|
|
3. What are the different scopes in JSP?
|
|
By: Barbara : 2008-12-09
|
|
Description: The scope of an object describes how widely it's available and who has access to it. For example, if an object is defined to have page scope, then it's available only for the duration of the current request on that page before being destroyed by the container. In this case, only the current page has access to this data, and no one else can read it. At the other end of the scale, if an object has application scope, then any page may use the data because it lasts for the duration of the application, which means until the container is switched off. |
|
Read the full article
|
|
4. Using a DataSource from WebLogic in a JSP
|
|
By: Bruce W. Perry : 2008-11-24
|
|
Description: Example below imports the necessary classes at the top of the code using the page directive and its import attribute. Otherwise, this JSP accomplishes everything that the servlet of the prior recipe does, including the display of nearly identical output in the web browser. |
|
Read the full article
|
|
5. Getting HTTP Request Headers in a JSP
|
|
By: Bruce W. Perry : 2008-11-24
|
|
Description: The JSTL v1.0 makes all existing request headers available via the header implicit object. The JSTL automatically makes this variable available to JSPs; the header object evaluates to a java.util.Map type. |
|
Read the full article
|
|
6. Automatically Refreshing a JSP
|
|
By: Emiley J. : 2008-11-24
|
|
Description: The following scriptlet code adds a Refresh header that specifies a 60-second interval for refreshing the JSP. Place this code at the top of the JSP before any content appears: |
|
Read the full article
|
|
7. Embedding a QuickTime movie in a JSP
|
|
By: Bruce W. Perry : 2008-11-24
|
|
Description: Similar to using the Java Plug-in, a JSP uses the embed tag inside of an HTML object tag to properly load one of Apple Computer's QuickTime movies. You must include the CLASSID attribute value exactly as the below sample jsp program specifies. You also must include the same CODEBASE attribute value. If the user has an Internet Explorer Windows browser, but has not yet installed the QuickTime ActiveX control, the CODEBASE attribute value specifies where the user can download it. |
|
Read the full article
|
|
8. Embedding MP3 audio file in a JSP
|
|
By: Bruce W. Perry : 2008-11-24
|
|
Description: The embed tag is used to include an audio file with a JSP, so that when a user requests the JSP, the browser plays music. Specifically, the browser is designed to detect the MIME type of the embedded file, then activate a helper application such as QuickTime or RealAudio to handle the embedded file and play the music. |
|
Read the full article
|
|
9. Writing your first JSP page
|
|
By: Bruce W. Perry : 2008-11-23
|
|
Description: A JavaServer Pages (JSP) component is a type of Java servlet that is designed to fulfill the role of a user interface for a Java web application. Web developers write JSPs as text files that combine HTML or XHTML code, XML elements, and embedded JSP actions and commands. JSPs were originally designed around the model of embedded server-side scripting tools such as Microsoft Corporation's ASP technology; however, JSPs have evolved to focus on XML elements, including custom-designed elements, or custom tags, as the principal method of generating dynamic web content. |
|
Read the full article
|
|
10. Deploying an Individual JSP on Tomcat
|
|
By: Bruce W. Perry : 2008-11-23
|
|
Description: The easiest way to test a new JSP file is to place it at the top level of Tomcat's default web application. This application is located in the /webapps/ROOT/ directory. Tomcat 4.1.x compiles (or recompiles, if you are pasting a new JSP file over an old one) the JSP and display its response in a web page. You do not have to stop and start Tomcat using the Tomcat manager application for the new JSP file to be available to your web application. |
|
Read the full article
|
Next
|
|
![]() |
|