[ http://issues.apache.org/jira/browse/BEEHIVE-381?page=all ] Alejandro Ramirez closed BEEHIVE-381: -------------------------------------
Verified Fixed. Executed Repro steps and now @Jpf.Catch is putting the exception under a key created from the exception class name, as long as the 'messageKey' attribute was not specified. In addition, executed the coreWeb BVT "ExceptionMessages" which tests this scenario and it passed. > @Jpf.Catch does not put expression message into the right error key > ------------------------------------------------------------------- > > Key: BEEHIVE-381 > URL: http://issues.apache.org/jira/browse/BEEHIVE-381 > Project: Beehive > Type: Bug > Components: NetUI > Versions: V1Alpha, V1Beta > Reporter: Rich Feit > Assignee: Alejandro Ramirez > Fix For: V1Beta > > Repro: > - Add the following to a page flow: > @Jpf.Catch(type=IllegalStateException.class, path="error.jsp", > message="${pageFlow.URI}") > - In error.jsp, add the following tag: > <netui:error key="java.lang.IllegalStateException"/> > - Hit an action that throws IllegalStateException. > Expected: see the page flow's URI displayed in error.jsp > Actual: see nothing displayed in error.jsp. > @Jpf.Catch should put the exception under a key created from the exception > class name, as long as you didn't specify the 'messageKey' attribute. -- 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
