Page builder inputsAdded by IBM on August 31, 2010 | Version 1 (Original)
|This topic describes the inputs for the Page builder.
This topic describes the inputs for the Page builder.
Table 1. Page builder inputs
|Name||Enter a name for this builder call. The WebSphere® Portlet Factory Designer displays this name in the builder call list.|
|Page Contents (HTML)||Enter valid HTML or JSP syntax to create a page (see example). Make sure that the page contains an HTML tag that wraps the contents of the page, such as <html /> or <body />. |
<head><title>This is a Page</title></head>
<p><b>Author Info</b><br />
Author: Jdoe<br />
E-mail: email@example.com<br />
Phone: x1234<br />
<p>This is a page that incorporates JSP.<br />
Time is: <%=(new java.util.Date()).toString()%>
Below is a placeholder for a control: <br />
<span name="firstBuilder" />
|Make URLs Absolute||Enable to force the conversion of any relative URL on this page to an absolute URL.|
|Rename Existing||This input is useful in cases where you want to change the behavior of code that was placed in the WebApp by a high-level builder or by an Imported Model. |
For example, you might want to do this if you have a Domino View & Form builder in your model, and you want to use a different class for one of the LJOs that Builder adds to the WebApp. The Domino View and Form Builder does not provide an "LJO Class Name" input. But, you can place a new LJO Builder in the model and give it the same name as that assigned by the Domino View and From Builder, thus replacing the existing LJO and specifying new class.
When checked, this input will cause the Builder to replace an existing WebApp object with a new object. The Builder will locate the existing WebApp object (variable, LJO, and so on), rename it, and then create a replacement object.Note: This input is available on the following low-level builders that create WebApp objects: Action List, Imported Page, Linked Java Object, Linked Model, Method, Method Call, Page, Variable and Schema.
|Fully Parse Page||Normally, the IBM® WebSphere Portlet Factory runtime parses only nodes with a name attribute and certain special nodes, such as form, body, and head. Other nodes are left unparsed. The advantage of partial parsing is that it is more efficient, both in time and memory, and it makes the parser somewhat more tolerant of poorly-formed HTML. Many odd constructions of HTML that are tolerated by browsers but are not, in fact, legal HTML, can be overlooked by the more tolerant parser. |
Check this option to have the page fully parsed. This is especially useful to use advanced PageLocations on the page or when using XPath references in your PageLocations.
Parent topic: Page builder: wpf7