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/04/09 01:01:17 UTC
[jira] Updated: (BEEHIVE-400) Nice to have a way to inheriate all its JSPs members when inheriating a pageflow
[ http://issues.apache.org/jira/browse/BEEHIVE-400?page=history ]
Rich Feit updated BEEHIVE-400:
------------------------------
Fix Version: TBD
(was: V1)
I agree with this; however, I don't think we can get to it in the v1.0 timeframe. We should investigate for 1.1.
> Nice to have a way to inheriate all its JSPs members when inheriating a pageflow
> --------------------------------------------------------------------------------
>
> Key: BEEHIVE-400
> URL: http://issues.apache.org/jira/browse/BEEHIVE-400
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta, V1
> Reporter: Julie Zhuo
> Assignee: Rich Feit
> Fix For: TBD
>
> Currently when inheriate a pageflow, we have no way of inheriating all its JSPs that are referenced by relative path. What we need to do right now when we inheritate a pageflow is to copy all these jsp files into the child page flow directory and if there is one missing it will be a compiler warning and a runtime error. In the case of referencing the jsps by absolute path, it looses the databinding context to the child flow and instead it switches to the parent flow totaly.
--
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