Schema builder inputs - Portlet Factory v6.1.2

Portlet Factory, Version 6.1.2

Schema builder inputs

This topic describes the inputs for the Schema builder.

Table 1. Schema builder inputs
Input Name Description
Name Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Schema Source Type Enable the radio button that represents how this schema is to be provided. You have two choices:

Existing URL/File

Enter an indirect reference, URL, or file path (relative fromIBM® WebSphere Portlet Factory document root directory) that specifies the path to the schema.

Specify explicitly as builder input

In the text entry area displayed when this radio button is selected, enter the XML notation representing the schema you want to use.

URL or Schema File Location This input is available when Existing URL/File/Variable is selected above
Use the File Chooser to select one of the following:

Schema at a URL

The URL can be a http://, https: or file:// reference that is followed for schema generation at regen time.For example: http://www.myschemas.org/schemas/schema1.xsd

Schema on the current file system

file://c:\myschemas\schema1.xsd

Schema in or below WebSphere Portlet Factory's document root

schemas/book.xsd

Schema defined by the XML in a variable

A ${Variables/} reference is allowed in the URL field and provides an alternative means of getting a schema into the model as long as the variable has an initial value. (The variable content is not looked at after regen time.)For example: ${Variables/mySchema}.

Note: Schemas that define many elements could cause an "Out of memory" in the chooser that lets you determine the type for a variable or method argument.
Save Schema to File This input allows you to specify a file containing the defined schema. A Save As window allows you to specify the location and file name of the resulting XSD file.
Overwriting

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.

Enable

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.

Parent topic: Schema builder

Library | Support |

Input Name	Description
Name	Name for this builder call. The WebSphere Portlet Factory Designer displays this name in the builder call list.
Schema Source Type	Enable the radio button that represents how this schema is to be provided. You have two choices: Existing URL/File Enter an indirect reference, URL, or file path (relative fromIBM® WebSphere Portlet Factory document root directory) that specifies the path to the schema. Specify explicitly as builder input In the text entry area displayed when this radio button is selected, enter the XML notation representing the schema you want to use.
URL or Schema File Location	This input is available when Existing URL/File/Variable is selected above Use the File Chooser to select one of the following: Schema at a URL The URL can be a http://, https: or file:// reference that is followed for schema generation at regen time.For example: http://www.myschemas.org/schemas/schema1.xsd Schema on the current file system file://c:\myschemas\schema1.xsd Schema in or below WebSphere Portlet Factory's document root schemas/book.xsd Schema defined by the XML in a variable A ${Variables/} reference is allowed in the URL field and provides an alternative means of getting a schema into the model as long as the variable has an initial value. (The variable content is not looked at after regen time.)For example: ${Variables/mySchema}. Note: Schemas that define many elements could cause an "Out of memory" in the chooser that lets you determine the type for a variable or method argument.
Save Schema to File	This input allows you to specify a file containing the defined schema. A Save As window allows you to specify the location and file name of the resulting XSD file.
Overwriting
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. Enable 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.