Programming Tutorials

By: Jagan : 2007-10-06

Description: The TryCatchFinally interface was introduced in the JSP 1.2 specification. This interface provides a way to gracefully handle exceptions that may occur during the processing of classic tags, regardless of whether the tag implements the Tag, IterationTag, or BodyTag interface.

By: Ivan Lim : 2007-10-06

Description: The classic tags can evaluate their body content zero, or one or more, times. This is particularly useful when the content to be evaluated is trivial or, in other words, when no transformation or manipulation of the content is required before it's output to the page. If such transformation is required prior to the content being written to the page, you must turn to the BodyTag interface.

By: Henry : 2007-10-06

Description: The IterationTag interface was introduced as a part of the JSP 1.2 specification in an attempt to simplify the procedure for evaluating and reevaluating body content multiple times. This was previously possible with the JSP 1.1 BodyTag interface, although the implementation details were complex.

By: Fazal : 2007-10-06

Description: Introducing attributes into a custom tag does change the tag life cycle slightly because before the functionality of the tag can be executed (the doTag() method in the case of simple tags), the attributes must be passed to the tag handler so that they can be used by the tag. The way that the JSP specification allows this is through properties and setter methods of the tag handler class. A tag handler must have a property and a setter method for every attribute that it supports.

By: Charles : 2007-10-04

Description: Through the use of the and elements, you can automatically include a page before and after the evaluation of a group of pages. The element is a context-relative path that must correspond to an element in the web application. When the element is present, the given path will be automatically included (as in an include directive) at the beginning of each JSP page in this

By: Baski : 2007-10-04

Description: To enable or disable the evaluation of scripting elements within a page, you can use the element. By default, scripting is enabled. To disable scripting for all the JSP pages in your application, you can use a fragment similar to the following:

By: Abinaya : 2007-10-04

Description: To enable or disable the evaluation of the EL, you can use the element. This can be used to easily set the isELIgnored property of a group of JSP pages. By default, the EL evaluation is enabled for web applications using a Servlet 2.4 or Servlet 2.5 web.xml. To disable evaluation for all the JSP pages in our application, you can use a fragment similar to the following:

By: Baski : 2007-09-23

Description: In this tutorial, you'll look at the syntax of the EL, see how to use it on a JSP page, and learn the reserved words of the language. After you've looked at the basics, you'll move on to look at how and why you might disable the EL and Java scriptlets within a page or set of pages.

By: Abinaya : 2007-09-23

Description: One of the features of the JSP specification that you'll be using most often is the JSP expression language, an intentionally simple language that is, to a large extent, independent from JSP. In previous incarnations of JSP, Java code was embedded into JSP pages in the form of scriptlets, for example:

By: Daniel Malcolm : 2007-09-23

Description: Now you'll learn how you can use the EL within the body of a JSP page so that you can produce dynamic content. Listing below shows an example of a JSP page with some dynamic content generated by the EL. This page displays the value of a parameter (passed to the page) called name. The user is then given a text field in which to enter a new name, and a button to submit the name back to the page for another greeting.