JSP files used in a Commerce Enabled Portal follow the same guidelines as JSP files used in non portal WebSphere Commerce stores, with the following exceptions:
- In Commerce Enabled Portals, JSP files are returned to portlets as fragments, because a portlet only composes a portion of the portal page. The portal page is normally composed of several fragments. (See Commerce Enabled Portal architecture for more details). As a result, JSP files used in Commerce Enabled Portals must not include any page-level HTML tags, such as <html>, <head> or <body>.
- JSP files used in Commerce Enabled Portals should include a special set of tags that allow the files to work with WebSphere Portals. Commerce Enabled Portal provides a tag library of these tags. For more information, see Commerce Enabled Portal JSP file tag library.
For a better understanding and more examples of how these guidelines are implemented in a JSP file, complete the following tutorials:
- Commerce Enabled Portal tutorial: Understanding the development environment
- Commerce Enabled Portal tutorial: Adding a WebSphere Commerce feature to a Commerce Enabled Portal
If you are creating a Commerce Enabled Portal that can be accessed by Wireless Access Protocol (WAP), see Wireless Markup Language (WML) JSP files.
For more information about developing JSP files for use in WebSphere Commerce, see JSP page designer.