A new JSP looks like this:

<%@ taglib uri="http://www.atg.com/taglibs/daf/dspjspTaglib1_0" prefix="dsp" %>


  <title>A Simple Test Page</title>

<body bgcolor="#ffffff">
  <h1>A Simple Test Page</h1>



The Document Editor initially supplies these markup tags:

Other Items to import

To comply with the JSP specification, you must import any class you reference in a JSP to make it available to the page. For example, in order to embed Java in a tag and reference ATG specific classes, you must use an @import directive to make atg.servlet package available to the page. For example:

<%@ page import="atg.servlet.*"%>

Changing the tag library directive

A tag library can be deployed in two ways. By default, the DSP tag libraries tld files are kept in the tag library jar file inside WEBINF/lib. The URI used in JSP page directives are defined in the tld itself.

The URI in the page directive must match the URI specified in either the tag library’s tld file (as is the case with the DSP tag libraries) or web.xml. If you want to define a different URI for the DSP tag libraries, specify the new URI and tld location in web.xml. Then, you can use either the default or the new URI in your JSPs.

For instructions on making your J2EE application deployment-ready, see the J2EE information provided by your application server vendor.

If you prefer a prefix other than the default and wish to use the Document Editor, you must use one of the following URIs:

Then you need to modify the tag libraries web.xml file and the JSPs that use it.

Although you can set the URI to any value you want, a URI other than these three causes the Document Editor to disregard the prefix setting in the page directive and instead use the default (dsp).

When you change the prefix in the DSP tag libraries declaration statement, the Document Editor adjusts to the new prefix and provides it to any new tags you insert. Existing tags must be updated manually.

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices