You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Srinivas Surapaneni (JIRA)" <de...@beehive.apache.org> on 2006/06/16 14:01:30 UTC

[jira] Created: (BEEHIVE-1124) pageflow exception handlers problem

pageflow exception handlers problem
-----------------------------------

         Key: BEEHIVE-1124
         URL: http://issues.apache.org/jira/browse/BEEHIVE-1124
     Project: Beehive
        Type: Bug

    Reporter: Srinivas Surapaneni


The new exception handler is having problem when you don't specify either message or messageKey

Temporarily we are putting message="" as a workaround

@Jpf.Catch(type = ReferentialConstraintException.class, message = "", method = "referentialConstraintCannotDeletedHandler")

We want to create the ActionMessage in the handler method and not on the annotation

The way it is working now is inflexible

We are using it as a workaround. But there will be 2 messages, 1 blank and 1 we are putting in the handler method


-- 
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] Updated: (BEEHIVE-1124) pageflow exception handlers problem

Posted by "Eddie O'Neil (JIRA)" <de...@beehive.apache.org>.
     [ http://issues.apache.org/jira/browse/BEEHIVE-1124?page=all ]

Eddie O'Neil updated BEEHIVE-1124:
----------------------------------

    Component: NetUI
         type: Improvement  (was: Bug)
      Version: 1.0.1

Just fixing up fields here...  Also reclassified as an improvement as the description states that this works as designed.

> pageflow exception handlers problem
> -----------------------------------
>
>          Key: BEEHIVE-1124
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-1124
>      Project: Beehive
>         Type: Improvement

>   Components: NetUI
>     Versions: 1.0.1
>     Reporter: Srinivas Surapaneni

>
> The new exception handler is having problem when you don't specify either message or messageKey
> Temporarily we are putting message="" as a workaround
> @Jpf.Catch(type = ReferentialConstraintException.class, message = "", method = "referentialConstraintCannotDeletedHandler")
> We want to create the ActionMessage in the handler method and not on the annotation
> The way it is working now is inflexible
> We are using it as a workaround. But there will be 2 messages, 1 blank and 1 we are putting in the handler method

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