Entering content frame

Background documentation Tag Lib Packaging Locate the document in its SAP Library structure

All Java Server Pages (JSP) that are compiled in a portal component can use custom tags lib by following the rules described below:

The class file that implements the tag lib definition must be packaged in the lib or classes directory of the portal component PAR file.

The JSP file that references the tag library can use the custom tag library definition property to reference the tag Library as follows:

 

<%@ taglib uri="[uri]" prefix="custom" %>

 

[uri]

Directory

Description

Profile

.../.../custom.tld

Same as current JSP

Takes the tag library definition file relatively to the current JSP 

None

prt:taglib:custom

private folders

The tag library is referenced by an identifier that must be defined in the profile of the component. The ID here is custom. If the JSP page is included in a component as a resource, the tag library must be defined in the profile of the component.

custom=/taglib/custom.tld

Using the Taglib Provided by the Portal Services

All JSPs that are compiled in a portal component can use tag libraries provided by the portal service by following the rules described below:

The tag lib definition file must be referenced in the portal component profile as follows:

Property

Value

tlhtmlb

/SERVICE/htmlb/taglib/htmlb.tld

The JSP file that references the tag library can use the custom tag library definition property to reference the tag Library as follows:

 

<%@ taglib uri="prt:taglib:tlhtmlb" prefix="hbj" %>

 

 

Leaving content frame