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)" <be...@incubator.apache.org> on 2005/02/04 00:52:28 UTC
[jira] Assigned: (BEEHIVE-234) Confusing errors when hitting a page flow whose class is missing or not accessible
[ http://issues.apache.org/jira/browse/BEEHIVE-234?page=history ]
Rich Feit reassigned BEEHIVE-234:
---------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
> 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: Alejandro Ramirez
> 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