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 2007/10/03 16:29:50 UTC
[jira] Updated: (JUDDI-74) Make the Database tables used by jUDDI
to be configurable
[ https://issues.apache.org/jira/browse/JUDDI-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam updated JUDDI-74:
---------------------------
Fix Version/s: 2.0
> Make the Database tables used by jUDDI to be configurable
> ---------------------------------------------------------
>
> Key: JUDDI-74
> URL: https://issues.apache.org/jira/browse/JUDDI-74
> Project: jUDDI
> Issue Type: Wish
> Components: Feature Requests Section
> Affects Versions: 2.0
> Reporter: Anil Saldhana
> Assignee: Kurt Stam
> Priority: Minor
> Fix For: 2.0
>
>
> In a managed environment like a J2EE server, it is great to be able to configure every small bit of the subsystems it includes. Along the same lines, I would like to propose making the database table names used by jUDDI internally to be configurable as it uses very common tables like "Address", "BusinessEntity" etc. As a user, I should be able to rename the table to something like "JuddiAddress", "JuddiBusinessEntity" etc so that I can distibuish which tables belong to jUDDI and which belong to the application.
> This task involves updating the datastore functional java classes and the DB scripts.
--
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