Exporting DEFAULT_ page components
|Date:||27 July, 2005|
|Product/Release:||LANSA for Web|
|Abstract:||Creating Page Components for DEFAULT_ components there is a need to export them|
|Submitted By:||LANSA Technical Support|
|Last Review:||December 2010|
It is possible to create process specific pages as part of a Web application. The steps for doing this are described in the LANSA for Web Developer's View. The manual also states that any "process specific pages created for any standard pages prefixed by DEFAULT_ does not need to be registered as a Web component". Even though process specific pages are not registered as Web components, during a LANSA export these process specific pages will get included in the export list because they are part of the process information.
However, if the LANSA export facility is used to export DEFAULT_ pages, these pages will not be available to add to the export list when the option to "Add Web Components to List" is taken. There is a simple workaround to this whereby a Web component is created in the LANSA Web Administrator for the DEFAULT_ pages that you wish to export, so that they are then available on the list of Web components to export.
Exporting any of the DEFAULT_ pages is a powerful and potentially dangerous thing to do because when this version of the DEFAULT_ page is exported or imported into a target host this is effectively removing any DEFAULT_ pages that previously existed on the target machine. The user should be certain that this version of the DEFAULT_ pages is to be exported or imported before using this workaround.