You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt Stam (JIRA)" <ju...@ws.apache.org> on 2008/09/10 16:46:46 UTC
[jira] Created: (JUDDI-133) Add configuration manager
Add configuration manager
-------------------------
Key: JUDDI-133
URL: https://issues.apache.org/jira/browse/JUDDI-133
Project: jUDDI
Issue Type: Task
Reporter: Kurt Stam
Assignee: Kurt T Stam
Fix For: 3.0
We will need code to read the juddi configuration. We can port the one from 2.0 or use a a project like apache configuration. We probably should use something of the shelve rather then coding it ourselves. Another choice we need to make it whether the config file should be xml or a property file like we have in 2.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org
[jira] Closed: (JUDDI-133) Add configuration manager
Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam closed JUDDI-133.
---------------------------
Resolution: Fixed
We added Apache commons Configuration
> Add configuration manager
> -------------------------
>
> Key: JUDDI-133
> URL: https://issues.apache.org/jira/browse/JUDDI-133
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt Stam
> Assignee: Kurt T Stam
> Fix For: 3.0
>
>
> We will need code to read the juddi configuration. We can port the one from 2.0 or use a a project like apache configuration. We probably should use something of the shelve rather then coding it ourselves. Another choice we need to make it whether the config file should be xml or a property file like we have in 2.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org
[jira] Updated: (JUDDI-133) Add configuration manager
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-133:
------------------------------
Fix Version/s: (was: 3.0)
3.0alpha
> Add configuration manager
> -------------------------
>
> Key: JUDDI-133
> URL: https://issues.apache.org/jira/browse/JUDDI-133
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.0alpha
>
>
> We will need code to read the juddi configuration. We can port the one from 2.0 or use a a project like apache configuration. We probably should use something of the shelve rather then coding it ourselves. Another choice we need to make it whether the config file should be xml or a property file like we have in 2.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.