So are you saying that overriding an action means also adding a jsp at
that level?

- john

-----Original Message-----
From: Rich Feit [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 23, 2005 2:44 PM
To: Beehive Developers
Subject: Re: inheriting pages in page flows

Hi John,

I agree that this would be ideal, but I don't think it's possible 
(should have made it clear in the original email).  There's no way at 
build time to know for certain whether a local path is "present", and 
there's also no way at runtime to know if it's "present" beyond trying 
to hit it and looking for a 404 result.  This is true for JSPs as well 
as for other arbitrary Servlet paths.

Rich

John Rohrlich wrote:

>A good start Rich, but I'd like to see some additional behavior.
>
>Allow action overrides to use pages local to the overridden actions
page
>flow directory if the page is not found local to the overriding class.
>This should work for n levels of inheritance. If class B extends class
>C, and class A extends class B, and both extending classes override the
>same action then you would first look for a jsp in A's directory. If
you
>didn't find the jsp you would look in B's directory and then finally
C's
>directory.
>
>- john
>
>
>
>-----Original Message-----
>From: Rich Feit [mailto:[EMAIL PROTECTED] 
>Sent: Thursday, June 23, 2005 11:13 AM
>To: Beehive Developers
>Subject: inheriting pages in page flows
>
>Hi all,
>
>I'd like some design feedback here.  
>http://issues.apache.org/jira/browse/BEEHIVE-400 deals with a
much-asked
>
>question: if you have a page flow that inherits from another page flow,

>how can you also inherit pages from the base page flow?  Currently, 
>there's no good way to do it, which is an obvious hole.  My thought is 
>to do something really simple (from the user's point of view :) ), like

>have a class-level annotation attribute:
>
>    inheritLocalPaths=true
>
>This would cause local paths in *inherited* actions to be used in the 
>context of the current page flow.  I think this might be sufficient,
and
>
>even if it turns out it's not, it seems like a good start.  Any 
>thoughts/comments on this?
>
>Thanks,
>Rich
>
>
>
>  
>


Reply via email to