You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <de...@beehive.apache.org> on 2005/09/24 05:15:34 UTC

[jira] Created: (BEEHIVE-954) form bean-specifc message bundle does not work when two actions use the same form bean

form bean-specifc message bundle does not work when two actions use the same form bean
--------------------------------------------------------------------------------------

         Key: BEEHIVE-954
         URL: http://issues.apache.org/jira/browse/BEEHIVE-954
     Project: Beehive
        Type: Bug
  Components: NetUI  
    Versions: V1, v1m1    
    Reporter: Rich Feit
 Assigned to: Rich Feit 
     Fix For: 1.1


This bug was sent to me by Nathan Olson.

Repro:
    - Create a form bean class that has its own messages, using a @Jpf.FormBean annotation with its 'messageBundle' attribute set to a valid message bundle.

    - In the form bean class, create a validation rule that refers to one of the message keys.

    - Create a page flow with two different actions which use the form bean class you made.  Make sure each of the actions has a validationErrorForward.

    - Create a JSP or JSPs that submit to each of the two actions.  Each JSP should have a <netui:errors/> tag in it, to display the validation messages.

    - Submit forms to each of the two actions, and make sure to use input that will fail validation.

EXPECTED: each of the actions produces a validation error message.
ACTUAL: one of the actions produces a tag error that says something like "Could not find a message for message key "XXXXX" in the default message bundle for the current page flow."

cannot be found in the default message bundle

-- 
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


[jira] Closed: (BEEHIVE-954) form bean-specifc message bundle does not work when two actions use the same form bean

Posted by "Julie Zhuo (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-954?page=all ]
     
Julie Zhuo closed BEEHIVE-954:
------------------------------


Verified with rev354233. Both actions produce validation error messages now. Close. 


> form bean-specifc message bundle does not work when two actions use the same form bean
> --------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-954
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-954
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1, v1m1
>     Reporter: Rich Feit
>     Assignee: Julie Zhuo
>      Fix For: 1.1

>
> This bug was sent to me by Nathan Olson.
> Repro:
>     - Create a form bean class that has its own messages, using a @Jpf.FormBean annotation with its 'messageBundle' attribute set to a valid message bundle.
>     - In the form bean class, create a validation rule that refers to one of the message keys.
>     - Create a page flow with two different actions which use the form bean class you made.  Make sure each of the actions has a validationErrorForward.
>     - Create a JSP or JSPs that submit to each of the two actions.  Each JSP should have a <netui:errors/> tag in it, to display the validation messages.
>     - Submit forms to each of the two actions, and make sure to use input that will fail validation.
> EXPECTED: each of the actions produces a validation error message.
> ACTUAL: one of the actions produces a tag error that says something like "Could not find a message for message key "XXXXX" in the default message bundle for the current page flow."
> cannot be found in the default message bundle

-- 
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


[jira] Assigned: (BEEHIVE-954) form bean-specifc message bundle does not work when two actions use the same form bean

Posted by "Alejandro Ramirez (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-954?page=all ]

Alejandro Ramirez reassigned BEEHIVE-954:
-----------------------------------------

    Assign To: Julie Zhuo  (was: Alejandro Ramirez)

Please verify in 1.1

> form bean-specifc message bundle does not work when two actions use the same form bean
> --------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-954
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-954
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1, v1m1
>     Reporter: Rich Feit
>     Assignee: Julie Zhuo
>      Fix For: 1.1

>
> This bug was sent to me by Nathan Olson.
> Repro:
>     - Create a form bean class that has its own messages, using a @Jpf.FormBean annotation with its 'messageBundle' attribute set to a valid message bundle.
>     - In the form bean class, create a validation rule that refers to one of the message keys.
>     - Create a page flow with two different actions which use the form bean class you made.  Make sure each of the actions has a validationErrorForward.
>     - Create a JSP or JSPs that submit to each of the two actions.  Each JSP should have a <netui:errors/> tag in it, to display the validation messages.
>     - Submit forms to each of the two actions, and make sure to use input that will fail validation.
> EXPECTED: each of the actions produces a validation error message.
> ACTUAL: one of the actions produces a tag error that says something like "Could not find a message for message key "XXXXX" in the default message bundle for the current page flow."
> cannot be found in the default message bundle

-- 
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


[jira] Resolved: (BEEHIVE-954) form bean-specifc message bundle does not work when two actions use the same form bean

Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-954?page=all ]
     
Rich Feit resolved BEEHIVE-954:
-------------------------------

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

Fixed with revision 291240.

> form bean-specifc message bundle does not work when two actions use the same form bean
> --------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-954
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-954
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1, v1m1
>     Reporter: Rich Feit
>     Assignee: Alejandro Ramirez
>      Fix For: 1.1

>
> This bug was sent to me by Nathan Olson.
> Repro:
>     - Create a form bean class that has its own messages, using a @Jpf.FormBean annotation with its 'messageBundle' attribute set to a valid message bundle.
>     - In the form bean class, create a validation rule that refers to one of the message keys.
>     - Create a page flow with two different actions which use the form bean class you made.  Make sure each of the actions has a validationErrorForward.
>     - Create a JSP or JSPs that submit to each of the two actions.  Each JSP should have a <netui:errors/> tag in it, to display the validation messages.
>     - Submit forms to each of the two actions, and make sure to use input that will fail validation.
> EXPECTED: each of the actions produces a validation error message.
> ACTUAL: one of the actions produces a tag error that says something like "Could not find a message for message key "XXXXX" in the default message bundle for the current page flow."
> cannot be found in the default message bundle

-- 
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