[ http://issues.apache.org/jira/browse/BEEHIVE-494?page=history ]
Rich Feit resolved BEEHIVE-494:
-------------------------------
Assign To: Alejandro Ramirez (was: Rich Feit)
Resolution: Invalid
This is actually by design. Since the page flow is abstract, you *must* extend
it in order to access that forward... and in that case, one of two things is
possible:
1) the derived page flow will be missing the referenced file, in which case
a warning will be printed, or,
1) the derived page flow will contain the referenced file, in which case a
warning is not necessary.
> The compiler is not displaying warnings for invalid paths in abstract
> pageFlows
> -------------------------------------------------------------------------------
>
> Key: BEEHIVE-494
> URL: http://issues.apache.org/jira/browse/BEEHIVE-494
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Alejandro Ramirez
> Assignee: Alejandro Ramirez
> Priority: Minor
> Fix For: V1
> Attachments: simpleInvalidPathWarning.zip
>
> 1.- Compile the attached pageFlow (NOTE: the index.jsp page for the begin
> action does not exist)
> The pageFlow looks like:
> @Jpf.Controller(simpleActions={
> @Jpf.SimpleAction(name="begin", path="index.jsp")})
> public abstract class ParentFlow
> extends PageFlowController
> {
>
> }
> Expected: The compiler should display a warning about not being able to find
> the index.jsp page that the simple action "begin" refers to.
> Actual: The compiler does not throw a warning (NOTE: This only happens if
> you declare the pageFlow as abstract. If you declare it as a regular class,
> then the compiler displays the warning).
--
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
