Developing > Persistence layer > WebSphere Commerce integration with WebSphere Portal > Customizing WebSphere Commerce Portal integration > Use the provided WebSphere Commerce MVCPortlet class (MVC style) > WebSphere Commerce Portal integration event handlers

---

WebSphere Commerce portlet render handler

The WebSphere Commerce Portlet render handler should not call the WebSphere Commerce services. Instead, it simply checks for the current state and mode of the portlet in order to determine the appropriate JSP path to be used when calling the request dispatcher.

To create a new customized version of the WebSphere Commerce Portlet render handler, the new code must implement the com.ibm.commerce.foundation.client.portal.handlers.PortletRenderHandler interface.

Here is an example of how to define a JSP template for rendering:

try {
 PortletRequestDispatcher requestDispatcher = 
 iPortlet.getPortletContext().getRequestDispatcher("/jsp/html/catalog/ProductDisplay.jsp");
 requestDispatcher.include(getRenderRequest(), getRenderResponse());
} 
catch (IOException e) {
 throw new PortletException(e);
}

Related concepts

WebSphere Commerce integration with WebSphere Portal

Use WebSphere Commerce services in portlets

WebSphere Commerce Portal integration event handlers

Related tasks

Calling a WebSphere Commerce service using the MVC portlet configuration file

Last updated: 25 November 2009