Entering content frame

Component documentation JSP Support Locate the document in its SAP Library structure

Purpose

The PRT supports two ways of using JSPs in the portal:

·        Declarative way

The JSP lives in the portal as a component on its own

·        Programmatic way

Any portal component can access any JSP provided with its PAR file, or which belongs to another portal component

This graphic is explained in the accompanying text

When a portal application uses a JSP resource containing double-byte characters, the portal runtime needs to know the character set that has been used to create the file. Thus the portal runtime can parse the file in the correct encoding and generates the corresponding portal component in UTF-8 encoding (or in any encoding specified in the runtime.doubleByteSupport.encoding property).

This is done by specifying the encoding in which the page has been saved in the pageEnconding directive of the JSP file:

<html>

<%@page pageEncoding=”shift_JIS” %>

...

 

 

See also:

 

·        Declaring JSP as a Portal Component

·        JSP Selected Programmatically

·        JSP Packaging/Compilation

·        Accessible JSP Objects

·        Tag Lib Packaging

·        Java Beans

·        Request Events Handling

 

 

Leaving content frame