You can find the original, high resolution video tutorial at: www.scja.com You can also find links to purchase my JSR168 Portlet Programming Book. :) Action Processing in a JSR-168 Portlet Strictly speaking, the various do methods of a portlet should only be responsible for generating the markup that needs to be sent back to the client. Since portlet mode methods, such as doView, doEdit, doConfigure and doHelp, are really only intended for generating the markup that gets sent back to the client, those methods are said to be part of the portlet?s rendering phase, and as such, these methods are passed a RenderRequest and a RenderResponse object. Two Phase Portlet Processing Tasks such as state management, form handling and PortletSession management should not take place during the portlet rendering phase. In fact, certain tasks, such as the manipulation the PortletPreferences object associated with the doEdit mode, or forcing a portlet to display itself in a maximized state, simply can?t be performed during the portlet rendering phase. Such tasks must be performed before a portlet is asked to render itself, during an important stage known as the event processing or action processing phase. The event processing phase is associated with a special method called processAction. This portorial examines how to take advantage of the action processing phase of a portlet. Please support our site, link to us, buy some books, and remember: Happy Java! Download the Code!!! (Scroll down <b>...</b>