You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org> on 2005/02/24 17:37:52 UTC
[jira] Created: (BEEHIVE-352) developer written netui-config files need to be merged with the default netui-config file
developer written netui-config files need to be merged with the default netui-config file
-----------------------------------------------------------------------------------------
Key: BEEHIVE-352
URL: http://issues.apache.org/jira/browse/BEEHIVE-352
Project: Beehive
Type: Improvement
Components: NetUI
Versions: V1Beta
Reporter: Eddie O'Neil
Assigned to: Eddie O'Neil
NetUI uses the netui-config file to configure the runtime with a set of "default" parameters. These include the expression language, interceptors, and prefix handlers.
Beehive developers have the ability to define a new netui-config.xml file which changes / extends these config parameters, but this needs to be done in a way that doesn't require duplicating all of the "default" config options in a user-defined netui-config.xml file.
So, there needs to be some kind of override / fallback mechanism that facilitates this.
--
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
[jira] Commented: (BEEHIVE-352) developer written netui-config files need to be merged with the default netui-config file
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-352?page=comments#action_66641 ]
Rich Feit commented on BEEHIVE-352:
-----------------------------------
When this is resolved, docs/forrest/src/documentation/content/xdocs/pageflow/config/beehive-netui-config.xml should be updated to remove the workaround instructions for creating a default beehive-netui-config.xml.
> developer written netui-config files need to be merged with the default netui-config file
> -----------------------------------------------------------------------------------------
>
> Key: BEEHIVE-352
> URL: http://issues.apache.org/jira/browse/BEEHIVE-352
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta, V1
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: TBD
>
> NetUI uses the netui-config file to configure the runtime with a set of "default" parameters. These include the expression language, interceptors, and prefix handlers.
> Beehive developers have the ability to define a new netui-config.xml file which changes / extends these config parameters, but this needs to be done in a way that doesn't require duplicating all of the "default" config options in a user-defined netui-config.xml file.
> So, there needs to be some kind of override / fallback mechanism that facilitates this.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-352) developer written netui-config files need to be merged with the default netui-config file
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-352?page=history ]
Eddie O'Neil updated BEEHIVE-352:
---------------------------------
Fix Version: V1
> developer written netui-config files need to be merged with the default netui-config file
> -----------------------------------------------------------------------------------------
>
> Key: BEEHIVE-352
> URL: http://issues.apache.org/jira/browse/BEEHIVE-352
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: V1
>
> NetUI uses the netui-config file to configure the runtime with a set of "default" parameters. These include the expression language, interceptors, and prefix handlers.
> Beehive developers have the ability to define a new netui-config.xml file which changes / extends these config parameters, but this needs to be done in a way that doesn't require duplicating all of the "default" config options in a user-defined netui-config.xml file.
> So, there needs to be some kind of override / fallback mechanism that facilitates this.
--
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
[jira] Updated: (BEEHIVE-352) developer written netui-config files need to be merged with the default netui-config file
Posted by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-352?page=all ]
Eddie O'Neil updated BEEHIVE-352:
---------------------------------
Version: V1
Fix Version: TBD
(was: V1)
Don't think this can happen before the release; moving to TBD...
> developer written netui-config files need to be merged with the default netui-config file
> -----------------------------------------------------------------------------------------
>
> Key: BEEHIVE-352
> URL: http://issues.apache.org/jira/browse/BEEHIVE-352
> Project: Beehive
> Type: Improvement
> Components: NetUI
> Versions: V1Beta, V1
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Fix For: TBD
>
> NetUI uses the netui-config file to configure the runtime with a set of "default" parameters. These include the expression language, interceptors, and prefix handlers.
> Beehive developers have the ability to define a new netui-config.xml file which changes / extends these config parameters, but this needs to be done in a way that doesn't require duplicating all of the "default" config options in a user-defined netui-config.xml file.
> So, there needs to be some kind of override / fallback mechanism that facilitates this.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira