You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org> on 2005/07/07 03:01:09 UTC
[jira] Created: (GERONIMO-722) Relocate jUDDI tables to their own schema
Relocate jUDDI tables to their own schema
-----------------------------------------
Key: GERONIMO-722
URL: http://issues.apache.org/jira/browse/GERONIMO-722
Project: Geronimo
Type: Sub-task
Reporter: Jeremy Boynes
The tables for the repositories database currently reside in the default schema.
These should be moved to their own schema (suggestion JUDDI) to avoid conflict with future applications.
This may involve creating a new DataSource definition.
--
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: (GERONIMO-722) Relocate jUDDI tables to their own schema
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-722?page=all ]
Matt Hogstrom updated GERONIMO-722:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
Moving to 1.x
> Relocate jUDDI tables to their own schema
> -----------------------------------------
>
> Key: GERONIMO-722
> URL: http://issues.apache.org/jira/browse/GERONIMO-722
> Project: Geronimo
> Type: Sub-task
> Components: webservices
> Versions: 1.0-M4
> Reporter: Jeremy Boynes
> Fix For: 1.x
>
> The tables for the repositories database currently reside in the default schema.
> These should be moved to their own schema (suggestion JUDDI) to avoid conflict with future applications.
> This may involve creating a new DataSource definition.
--
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] Commented: (GERONIMO-722) Relocate jUDDI tables to their own schema
Posted by "Stefan Schmidt (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-722?page=comments#action_12330327 ]
Stefan Schmidt commented on GERONIMO-722:
-----------------------------------------
This would be a very nice feature.
Currently, all juddi tables reside in the SystemDatabase which makes them hard to distinguish let alone backups. It would be nice, when the user selects 'install JUDDI' during Geronimo installation, if a Derby database named jUDDI would be created in var/derby and populated with the db2 'create_database.sql' script which is included in the jUDDI distribution. I have tested this script already. Is it possible to make juddi incl. the database available via a GBean rather than a Web application by default?
Thanks.
Stefan Schmidt
> Relocate jUDDI tables to their own schema
> -----------------------------------------
>
> Key: GERONIMO-722
> URL: http://issues.apache.org/jira/browse/GERONIMO-722
> Project: Geronimo
> Type: Sub-task
> Components: webservices
> Versions: 1.0-M4
> Reporter: Jeremy Boynes
> Fix For: 1.0
>
> The tables for the repositories database currently reside in the default schema.
> These should be moved to their own schema (suggestion JUDDI) to avoid conflict with future applications.
> This may involve creating a new DataSource definition.
--
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: (GERONIMO-722) Relocate jUDDI tables to their own schema
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-722?page=all ]
David Jencks closed GERONIMO-722:
---------------------------------
Fix Version: 1.0
(was: 1.x)
Resolution: Fixed
Assign To: David Jencks
I implemented this in rev 354009 but could not find this issue.
> Relocate jUDDI tables to their own schema
> -----------------------------------------
>
> Key: GERONIMO-722
> URL: http://issues.apache.org/jira/browse/GERONIMO-722
> Project: Geronimo
> Type: Sub-task
> Components: webservices
> Versions: 1.0-M4
> Reporter: Jeremy Boynes
> Assignee: David Jencks
> Fix For: 1.0
>
> The tables for the repositories database currently reside in the default schema.
> These should be moved to their own schema (suggestion JUDDI) to avoid conflict with future applications.
> This may involve creating a new DataSource definition.
--
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: (GERONIMO-722) Relocate jUDDI tables to their own schema
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-722?page=all ]
Aaron Mulder updated GERONIMO-722:
----------------------------------
Component: webservices
Fix Version: 1.0
Version: 1.0-M4
> Relocate jUDDI tables to their own schema
> -----------------------------------------
>
> Key: GERONIMO-722
> URL: http://issues.apache.org/jira/browse/GERONIMO-722
> Project: Geronimo
> Type: Sub-task
> Components: webservices
> Versions: 1.0-M4
> Reporter: Jeremy Boynes
> Fix For: 1.0
>
> The tables for the repositories database currently reside in the default schema.
> These should be moved to their own schema (suggestion JUDDI) to avoid conflict with future applications.
> This may involve creating a new DataSource definition.
--
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