geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Schmidt (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-722) Relocate jUDDI tables to their own schema
Date Fri, 23 Sep 2005 23:34:31 GMT
    [ 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


Mime
View raw message