beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Ramirez (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Closed: (BEEHIVE-172) SharedFlows are not able to use Message Bundles in exception handlers
Date Tue, 10 May 2005 18:25:05 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-172?page=all ]
     
Alejandro Ramirez closed BEEHIVE-172:
-------------------------------------


Verified fixed.  Executed the repro steps and now we get the correct message from the bundle.
 I've also attached a new version of the repro steps in case we ever need to re-open this
issue.

> SharedFlows are not able to use Message Bundles in exception handlers
> ---------------------------------------------------------------------
>
>          Key: BEEHIVE-172
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-172
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>  Environment: Windows XP, tomcat.
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>      Fix For: V1
>  Attachments: NewReproPageflow.zip, pageFlows.zip
>
> 1.- Using the attached pageflows, add them to an existing beehive enabled webapp.
> 2.- Deploy your webapp and access the /SharedFlowTest/SharedFlowController.jpf.  In there,
click the link "Go to Exception Tests".
> 3.- Next in the "ExceptionTest - Start Page", click the "handle a global exception with
a method in /SharedFlowTest/SharedFlow.jpf " link.
> Expected: You should be taken to the "Error Page" and the page should display the following
value for "Message from method":
> caught SharedFlowTest.SharedFlowController$SharedFlowExceptionCatchByMethod: this is
a SharedFlowTest.sharedFlowExceptionCatchByMethod in SharedFlowTest.SharedFlow.methodHandler();
message = This message came from exceptionMessages.  The exception was Caught by the shared
flow: /SharedFlowTests/SharedFlow.jpfs
> Actual: The page displays the following value for "Message from method":
>  Message from method: caught SharedFlowTest.SharedFlowController$SharedFlowExceptionCatchByMethod:
this is a SharedFlowTest.sharedFlowExceptionCatchByMethod in SharedFlowTest.SharedFlow.methodHandler();
message = null 
> In other words, it seems like the "/SharedFlowTest/SharedFlow.jpfs" shared flow that
is handling the exception, is not able to access the resource bundle as specified in the following
annotation:
> @Jpf.Controller(
>     catches = {
>         @Jpf.Catch(
>             type = SharedFlowTest.SharedFlowController.SharedFlowExceptionCatchByMethod.class,
>             method = "methodHandler",
>             messageKey = "sharedFlowException")
>             //message = "This happened because of a GlobalCatchToMethodException")
>     },
>     messageResources = {
>         @Jpf.MessageResource(
>             name = "exceptionMessages")
>     })
> NOTE:  I have put the resource bundle named "exceptionMessages.properties" in the following
two places and none of them are picked up by the shared flow:
>     a) WEB-INF/resources/exceptionMessages.properties
>     b) WEB-INF/src/exceptionMessages.properties

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message