This topic outlines the differences between WebFacing portlet projects
and WebFacing Web projects.
When you create a new WebFacing project, you can create a new
J2EE 1.3 or 1.4 Struts WebFacing portlet project. You can also add a WebFacing
portlet to an existing non-struts based portlet project.
The following lists outline the differences to consider when working with
a WebFacing portlet project instead of a WebFacing Web project.
- Runtime
-
- Portlet projects must be run on a portal server or portal test environment.
They cannot be run on a Web application server.
- The default mode for keyboard text entry is insert mode for portlet projects
and it is not configurable in the Project Properties page.
The default mode for keyboard text entry is overwrite mode for Web projects
and is configurable in the Project Properties page.
For both portlet and Web projects, you can toggle insert key to enable either
insert mode or overwrite mode for the current page. Only WebFacing Web projects
maintain the mode that was selected by the end user on a previous Web page
to the next page. Auto tabbing is enabled by default for web project when
overwrite mode is configured as default. In WebFacing portlets, auto tabbing
is only enabled when you toggle the insert key to enable overwrite mode for
the current page.
- When multiple WebFacing applications are processing an INVITE operation
in the portal environment, only one INVITE timer will exist on the portal
page. This timer is for the WebFacing application which processed the last
request.
- WebFacing portlet projects do not support the following:
- Enable Web page compression in the project properties
under .
- Interoperability with HATS projects.
- WebFacing application bridge with other Web project such
as EGL
- Conversion
- The output of conversion for WebFacing portlet projects is the same as
WebFacing Web projects, however, the resulting HTML from the compiled JSPs
may differ to allow it to run in the Portal environment.
- A unique ID setting has been added to enable more than one portlet to
run in the same browser. You must follow the same code pattern that is used
in the WebFacing JavaScriptâ„¢ functions for Portal to ensure that
your Web settings will work for both Web and Portal environments.
- WebFacing portlet projects are created by default with the conversion
option Replace text with button for window records selected
in the Project Command Key Recognition properties page.
This places buttons in your window records so that they can easily be seen
in the compact portal Web page. To enable the same feature in a Web project,
you must select the project property, make the change (under ), save the changes, and then re-convert the project.
- Style
-