beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <>
Subject [jira] Resolved: (BEEHIVE-631) Message Bundles for Form Beans no longer seem to work
Date Tue, 10 May 2005 20:15:30 GMT
     [ ]
Rich Feit resolved BEEHIVE-631:

     Assign To: Alejandro Ramirez  (was: Rich Feit)
    Resolution: Fixed

Another good catch.  This was happening when there were messages associated with the form
bean (through @Jpf.FormBean), but there were no default messages associated with the page
flow.  Fixed with revision 169513.

> Message Bundles for Form Beans no longer seem to work
> -----------------------------------------------------
>          Key: BEEHIVE-631
>          URL:
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1
>     Reporter: Alejandro Ramirez
>     Assignee: Alejandro Ramirez
>      Fix For: V1
>  Attachments:
> Message Bundles declared within a form bean no longer seem to work.
> 1.- Unzip the attached pageflow into a beehive enabled webapp and access it (e.g. http://localhost:<yourport>/<yourContext>/validationTests/beanRules/BeanRulesController.jpf
> 2.- In the page that is displayed, click the "Click" button without entering any data.
> Expected:  There should be a message (obtained from a message bundle) that the required
rule is required.
> Actual:  There is an exception:
> Error Number	Tag Type	Error
> 1	Errors	Message	An error occurred accessing the message bundle. This may be because
there is no default message bundle defined for the current page flow
> I have made sure to include the declared bundle "beanScope" in WEB-INF/src and also verified
that after compilation of my webapp it is under WEB-INF/classes dir:
> @Jpf.Controller()
> public class BeanRulesController extends PageFlowController
> {
>     ...
>     @Jpf.FormBean(messageBundle = "beanScope")
>     public static class InnerBean extends FormData
>     {
>         ...
>     }
> }

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message