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)" <de...@beehive.apache.org> on 2005/09/01 17:18:09 UTC
[jira] Created: (BEEHIVE-904) change netui runtime to use JavaBean layer for config instead of XMLBeans
change netui runtime to use JavaBean layer for config instead of XMLBeans
-------------------------------------------------------------------------
Key: BEEHIVE-904
URL: http://issues.apache.org/jira/browse/BEEHIVE-904
Project: Beehive
Type: New Feature
Components: NetUI
Versions: v1m1, V1Beta, V1Alpha
Reporter: Eddie O'Neil
Assigned to: Eddie O'Neil
Priority: Blocker
Fix For: V1
This is a JIRA issue to track the progress of implementing the JavaBean cofiguration layer in NetUI that replaces direct access to the XMLBean from config clients.
The goal is to remove XMLBeans from the public API so that the configuration can be created via XML (currently parsed with an XMLBean), HiveMind, Spring, programmatically, etc.
The first part of this change has already been made -- the JavaBean layer has been checked in and is partially enabled in the runtime.
I'll attach a patch soon that makes this switch for the JPF runtime which has some slightly more detailed issues with back-compat and default values.
--
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] Resolved: (BEEHIVE-904) change netui runtime to use JavaBean layer for config instead of XMLBeans
Posted by "Eddie O'Neil (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-904?page=all ]
Eddie O'Neil resolved BEEHIVE-904:
----------------------------------
Resolution: Fixed
This work is now complete with SVN 279573. The JavaBean config layer is now the only way to access the configuration information.
> change netui runtime to use JavaBean layer for config instead of XMLBeans
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-904
> URL: http://issues.apache.org/jira/browse/BEEHIVE-904
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Alpha, V1Beta, v1m1
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Priority: Blocker
> Fix For: V1
> Attachments: beehive-904-patch.txt, beehive-904-patch.txt
>
> This is a JIRA issue to track the progress of implementing the JavaBean cofiguration layer in NetUI that replaces direct access to the XMLBean from config clients.
> The goal is to remove XMLBeans from the public API so that the configuration can be created via XML (currently parsed with an XMLBean), HiveMind, Spring, programmatically, etc.
> The first part of this change has already been made -- the JavaBean layer has been checked in and is partially enabled in the runtime.
> I'll attach a patch soon that makes this switch for the JPF runtime which has some slightly more detailed issues with back-compat and default values.
--
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-904) change netui runtime to use JavaBean layer for config instead of XMLBeans
Posted by "Eddie O'Neil (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-904?page=all ]
Eddie O'Neil updated BEEHIVE-904:
---------------------------------
Attachment: beehive-904-patch.txt
Patch for review that switches the Page Flow runtime onto the config beans.
There is one particular issue about URL formatting that will be in dev@ momentarily.
> change netui runtime to use JavaBean layer for config instead of XMLBeans
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-904
> URL: http://issues.apache.org/jira/browse/BEEHIVE-904
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: v1m1, V1Beta, V1Alpha
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Priority: Blocker
> Fix For: V1
> Attachments: beehive-904-patch.txt
>
> This is a JIRA issue to track the progress of implementing the JavaBean cofiguration layer in NetUI that replaces direct access to the XMLBean from config clients.
> The goal is to remove XMLBeans from the public API so that the configuration can be created via XML (currently parsed with an XMLBean), HiveMind, Spring, programmatically, etc.
> The first part of this change has already been made -- the JavaBean layer has been checked in and is partially enabled in the runtime.
> I'll attach a patch soon that makes this switch for the JPF runtime which has some slightly more detailed issues with back-compat and default values.
--
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-904) change netui runtime to use JavaBean layer for config instead of XMLBeans
Posted by "Eddie O'Neil (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-904?page=all ]
Eddie O'Neil updated BEEHIVE-904:
---------------------------------
Attachment: beehive-904-patch.txt
Update the patch for this to include fixes discussed in dev@ around the URL template factory class name's default value.
> change netui runtime to use JavaBean layer for config instead of XMLBeans
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-904
> URL: http://issues.apache.org/jira/browse/BEEHIVE-904
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: V1Alpha, V1Beta, v1m1
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Priority: Blocker
> Fix For: V1
> Attachments: beehive-904-patch.txt, beehive-904-patch.txt
>
> This is a JIRA issue to track the progress of implementing the JavaBean cofiguration layer in NetUI that replaces direct access to the XMLBean from config clients.
> The goal is to remove XMLBeans from the public API so that the configuration can be created via XML (currently parsed with an XMLBean), HiveMind, Spring, programmatically, etc.
> The first part of this change has already been made -- the JavaBean layer has been checked in and is partially enabled in the runtime.
> I'll attach a patch soon that makes this switch for the JPF runtime which has some slightly more detailed issues with back-compat and default values.
--
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] Closed: (BEEHIVE-904) change netui runtime to use JavaBean layer for config instead of XMLBeans
Posted by "Krista Baker (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-904?page=all ]
Krista Baker closed BEEHIVE-904:
--------------------------------
Have tried a variety of configurations and also created some basic JUnit tests for this feature to verify defaults and other basic configurations. Also verified that the xbeans jar is not included in the distribution for v1 rc3.
> change netui runtime to use JavaBean layer for config instead of XMLBeans
> -------------------------------------------------------------------------
>
> Key: BEEHIVE-904
> URL: http://issues.apache.org/jira/browse/BEEHIVE-904
> Project: Beehive
> Type: New Feature
> Components: NetUI
> Versions: v1m1, V1Beta, V1Alpha
> Reporter: Eddie O'Neil
> Assignee: Eddie O'Neil
> Priority: Blocker
> Fix For: V1
> Attachments: beehive-904-patch.txt, beehive-904-patch.txt
>
> This is a JIRA issue to track the progress of implementing the JavaBean cofiguration layer in NetUI that replaces direct access to the XMLBean from config clients.
> The goal is to remove XMLBeans from the public API so that the configuration can be created via XML (currently parsed with an XMLBean), HiveMind, Spring, programmatically, etc.
> The first part of this change has already been made -- the JavaBean layer has been checked in and is partially enabled in the runtime.
> I'll attach a patch soon that makes this switch for the JPF runtime which has some slightly more detailed issues with back-compat and default values.
--
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