Page flow exception

Question

I have one serious problem when handling exception in page flow. ie.
my code looks like,
// Generated by WebLogic Workshop
// Created on: Mon Dec 01 15:31:45 GMT+05:30 2003
// By: kshashishekar
package portlets.validation.validation;
import com.bea.wlw.netui.pageflow.FormData;
import com.bea.wlw.netui.pageflow.Forward;
import com.bea.wlw.netui.pageflow.PageFlowController;
import com.bea.wlw.netui.tags.html.TreeNode;
import javax.security.auth.login.FailedLoginException;
import javax.servlet.http.HttpServletRequest;
import org.apache.struts.action.ActionErrors;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.*;
import com.login.CustomLogin;
import com.bea.p13n.controls.login.UserLoginControl;
* @jpf:controller struts-merge="struts-config-portlets-validation-validation2.xml"
* @jpf:message-resources resources="validation.validator.Message"
* @jpf:view-properties view-properties::
* <!-- This data is auto-generated. Hand-editing this section is not recommended.
-->
* <view-properties>
* <pageflow-object id="pageflow:/portlets/validation/validation/validationController.jpf"/>
* <pageflow-object id="action:begin.do">
* <property value="280" name="x"/>
* <property value="60" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:validate1.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="220" name="x"/>
* <property value="200" name="y"/>
* </pageflow-object>
* <pageflow-object id="action:logout.do#portlets.validation.validation.validationController.ValidateForm">
* <property value="120" name="x"/>
* <property value="100" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:validate1Page1.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="384,320,320,256" name="elbowsX"/>
* <property value="172,172,192,192" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:validate1Page1.jsp">
* <property value="420" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="action-call:@page:Result.jsp@#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,170,170,184" name="elbowsX"/>
* <property value="332,332,203,203" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_2" name="toPort"/>
* </pageflow-object>
* <pageflow-object id="page:Result.jsp">
* <property value="120" name="x"/>
* <property value="340" name="y"/>
* </pageflow-object>
* <pageflow-object id="page:/error.jsp">
* <property value="40" name="x"/>
* <property value="180" name="y"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:begin.do@">
* <property value="316,350,350,384" name="elbowsX"/>
* <property value="52,52,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#Result.jsp#@action:validate1.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="184,170,170,156" name="elbowsX"/>
* <property value="192,192,332,332" name="elbowsY"/>
* <property value="West_1" name="fromPort"/>
* <property value="East_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="forward:path#success#validate1Page1.jsp#@action:logout.do#portlets.validation.validation.validationController.ValidateForm@">
* <property value="156,270,270,384" name="elbowsX"/>
* <property value="92,92,172,172" name="elbowsY"/>
* <property value="East_1" name="fromPort"/>
* <property value="West_1" name="toPort"/>
* <property value="success" name="label"/>
* </pageflow-object>
* <pageflow-object id="control:com.bea.p13n.controls.login.UserLoginControl#myControl">
* <property value="28" name="x"/>
* <property value="34" name="y"/>
* </pageflow-object>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#username#java.lang.String"/>
* <pageflow-object id="formbeanprop:portlets.validation.validation.validationController.ValidateForm#password#java.lang.String"/>
* <pageflow-object id="formbean:portlets.validation.validation.validationController.ValidateForm"/>
* </view-properties>
public class validationController extends PageFlowController
* This is the control used to generate this pageflow
* @common:control
private UserLoginControl myControl;
// Uncomment this declaration to access Global.app.
// protected global.Global globalApp;
// For an example of page flow exception handling see the example "catch"
and "exception-handler"
// annotations in {project}/WEB-INF/src/global/Global.app
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
protected Forward begin()
return new Forward( "success" );
* @jpf:action validation-error-page="validate1Page1.jsp"
* @jpf:forward name="success" path="Result.jsp"
* @jpf:catch method="exceptionHandler" type="Exception"
protected Forward validate1(ValidateForm aForm) throws Exception
com.bea.p13n.usermgmt.profile.ProfileWrapper var = myControl.login( aForm.username,
aForm.password, getRequest());
getRequest().setAttribute( "results", var );
return new Forward("success",aForm);
* Action encapsulating the control method :logout
* @jpf:action
* @jpf:forward name="success" path="validate1Page1.jsp"
* @jpf:catch message="not authenticated" path="/error.jsp" type="Exception"
public Forward logout( ValidateForm aForm )
throws Exception
myControl.logout( getRequest() );
return new Forward( "success" );
* @jpf:exception-handler
* @jpf:forward name="errorPage" path="/error.jsp"
protected Forward exceptionHandler( Exception ex, String actionName, String
message, FormData form )
String displayMessage = "An exception occurred in the action " + actionName;
System.out.println ("display message "+displayMessage);
getRequest().setAttribute( "errorMessage", displayMessage );
return new Forward( "errorPage" );
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class ValidateForm extends org.apache.struts.validator.ValidatorForm
private String password;
private String username;
public void setUsername(String username)
this.username = username;
public String getUsername()
return this.username;
public void setPassword(String password)
this.password = password;
public String getPassword()
return this.password;
* added just to test validate (override) method.
public ActionErrors validate(ActionMapping map, HttpServletRequest req)
ActionErrors errors = null;
try {
errors = super.validate(map,req);
}catch (Exception e)
e.printStackTrace();
if (errors ==null) {
System.out.println ("errors = "+errors);
} else
System.out.println ("errors= "+errors);
return errors;
in the above code when we call "validate1" action, it will authenticate successfully
when we enter valid username and passowrd.
But when i enter invalid credentials page flow controller should execute "handleException"
method but at this time i am getting an error
Page Flow Unhandled Exception
Exception: java.lang.IllegalArgumentException
Message: argument type mismatch
A java.lang.IllegalArgumentException exception was thrown and not handled by any
Page Flow. See the console for the exception stack trace.
please help us on how to rectify this error.
thanks,
shashi
[validationController.jpf]

Answer 1

Hi-
That may be on the right track, but the /index.jsp page gets displayed in the
portlet...I am still within the portal framework, so I don't think I am loosing
the context...
-Howie
"Khurram Zafar" <[email protected]> wrote:
>
you are most likely redirecting to the /error.jsp page and losing the
context for
your portal app. The index.jsp page may be defined as your <welcome-file>
in your
web.xml file. The best thing to do is to save the context before visiting
error.jsp
and then provide a link in error.jsp to go back. Look at javadoc for
PageURL for
obtaining the URL to a portal page, you can then save it in session of
pass it
to your error page.
"Howie Oakes" <[email protected]> wrote:
Hello-
I have a page flow portlet that I am testing some exception handling
on. Right
now when I catch an exception, I display the global /error.jsp page,
using the
@jpf:catch tag. The problem is when I refresh the page after viewing
the error
page, the pageflow always pulls up the /index.jsp page at the root of
the webapp.
I have to get a new session to see the original page flow.
This only happens when I am running the Jpf as a portlet...I don't see
this behavior
with it stand-alone.
I am not sure why the index.jsp page is being called...there are noreferences
to it in my jpf code...
thanks,
Howie