Hi. Instructions on how to remove yourself from mailing lists are here. http://incubator.apache.org/beehive/mailinglists.html
-----Original Message----- From: Rakesh Dhawan [mailto:[EMAIL PROTECTED] Sent: Thursday, January 20, 2005 6:29 AM To: Beehive Developers; [EMAIL PROTECTED] Subject: RE: [jira] Assigned: (BEEHIVE-174) MethodLevel Exception Handlers within sharedflows are not catching exceptions Please remove me from the mailing list -----Original Message----- From: Rich Feit (JIRA) [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 12:46 AM To: [email protected] Subject: [jira] Assigned: (BEEHIVE-174) MethodLevel Exception Handlers within sharedflows are not catching exceptions [ http://issues.apache.org/jira/browse/BEEHIVE-174?page=history ] Rich Feit reassigned BEEHIVE-174: --------------------------------- Assign To: Rich Feit > MethodLevel Exception Handlers within sharedflows are not catching exceptions > ------------------------------------------------------------------------ -- --- > > Key: BEEHIVE-174 > URL: http://issues.apache.org/jira/browse/BEEHIVE-174 > Project: Beehive > Type: Bug > Components: NetUI > Versions: V1Beta > Environment: windows xp, tomcat > Reporter: Alejandro Ramirez > Assignee: Rich Feit > Attachments: sharedflows.zip > > 1.- Place the attached pageflows within a beehive enabled webapp. > 2.- Deploy your webapp and access the following pageflow: /SharedFlowTest/SharedFlowController.jpf > That will display a jsp that has a link: "Go to Exception Tests". Click the link. > 3.- Next, in the "ExceptionTest Start Page" click the link: > "Method Level catch with a method in /SharedFlowTest/SharedFlow1/SharedFlow2/SharedFlow2.jpfs". > Expected: The link should throw an exception that should be caught by /SharedFlowTest/SharedFlow1/SharedFlow2/SharedFlow2.jpfs > Actual: The exception is thrown, but it is not caught. > If you look at the /SharedFlowTest/SharedFlowController.jpf, it contains a reference to the shared flow: > @Jpf.SharedFlowRef(name="sharedFlow2", type=SharedFlowTest.SharedFlow1.SharedFlow2.SharedFlow2.class) > Now, SharedFlowTest.SharedFlow1.SharedFlow2.SharedFlow2.jpfs contains an exception handler for the exception being thrown, but it seems like it is not being invoked: > @Jpf.ExceptionHandler( > forwards = { > @Jpf.Forward( > name = "errorPage2", > path = "sharedFlow2Error.jsp") > }) > protected Forward methodHandler( SharedFlow2MethodExceptionCatchByMethod ex, String actionName, > String message, Object form ) > { > messageFromMethod = "caught " + ex + " in /SharedFlowTest/SharedFlow1/SharedFlow2/SharedFlow2.jpfs; message = " + message; > return new Forward( "errorPage2" ); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
