9 1 8 Considerations for Using Web Components

9.1.8 Considerations for Using Web Components

Following are some important considerations when using Web components with Web functions:

• LANSA Web components are used in conjunction with the <RDML COMPONENT> tag. This tag instructs LANSA to process the Web component indicated by the tag.

• If you use the NAME keyword when creating your HTML Web component, do not use names longer than 10 characters. Some Browsers (e.g. Netscape) may cause the LWEB_JOB to fail by sending invalid data to the stack.

• Web components can be automatically embedded into an HTML page when the RDML function is compiled. Components are embedded based on the field name and the mode of the REQUEST or DISPLAY. For more details, refer to 9.1.6 Automatic Embedding of Web Components.

• Web components will be embedded for hidden fields in a display. The Web component will be defined as output mode for hidden fields. Defining hidden fields is a good method of embedding Web components.

• If you create a new Web component after your RDML functions have been compiled, you can manually edit the HTML page to use the <RDML COMPONENT> tag, or you can recompile your functions to automatically embed the components.

• You can change the definition of a component without recompiling your Web functions or editing your HTML pages.

• A LANSA Web component can be embedded into another LANSA Web component, provided they are not embedded recursively.

• You can embed Web components dynamically in your application by using the RDML COMPONENT tag with the &FLD option. For more details, refer to 9.1.7 Dynamically Embedding Web Components.

• LANSA Web components are created using the Web Function Editor. For more details, refer to Components Menu.

• Web components are defined at the partition level.

• Web component names must be unique in a partition. You may only duplicate a Web component name when there is a mode associated with the component. For example, you can create three components named DEPTMENT – one for Input mode, one for Output mode and one as Not Applicable.

• If you have manually created HTML pages using the Web Function Editor, these pages should be registered as Page components, especially if you need to export these pages with your system. (You should register the DEFAULT_xxxxxx pages as components if you need to export these pages. Refer to for information about Web Application Deployment.