[jira] Resolved: (BEEHIVE-234) Confusing errors when hitting a page flow whose class is missing or not accessible

["Rich Feit (JIRA)" <be...@incubator.apache.org>]

     [ http://issues.apache.org/jira/browse/BEEHIVE-234?page=history ]
     
Rich Feit resolved BEEHIVE-234:
-------------------------------

    Resolution: Fixed

Now, in all of these situations, you get the correct exception.

> Confusing errors when hitting a page flow whose class is missing or not accessible
> ----------------------------------------------------------------------------------
>
>          Key: BEEHIVE-234
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-234
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>     Versions: V1Beta
>     Reporter: Rich Feit
>     Assignee: Rich Feit
>      Fix For: V1Beta

>
> This bug covers three similar cases:
>     - You try and hit a page flow whose class is abstract.
>     - You try and hit a page flow whose class isn't compiled.
>     - You try and hit a page flow whose class isn't public.
> In all cases, an error is logged, but the user-visible error contains no usable information (assert or NPE in PageFlowRequestProcessor).  The most common situation is an uncompiled page flow.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira