| Summary: | jUDDI does not come with SQL scripts | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | JBossESB, Deployment | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.0.0 ER3 | CC: | dlesage |
| Target Milestone: | --- | ||
| Target Release: | 5.0.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1600 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-05-28 12:25:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jiri Pechanec
2009-11-16 08:01:14 UTC
Agreed in principle but the juddi release never came with scripts, so neither does our current (project) integration. Clarification - jUDDI v3 release never came with script, but SOA-P 4.x had come Correct, SOA-P 4.x came with the scripts because it used juddi v2. The juddi v2 codebase rolled its own persistence layer and, therefore, required (and provided) the scripts. If deemed needed the jUDDI project can create them as part of the jUDDI build and ship them. Or do we want to do this as part of productization? We try and push as much down into the projects to avoid update and and maintenance problems. For that reason we would prefer this to be driven by the project, but productisation will assist. http://issues.apache.org/jira/browse/JUDDI-329 scheduled for 3.0.1 mid jan, http://issues.apache.org/jira/browse/JUDDI-329 http://svn.apache.org/repos/asf/webservices/juddi/tags/juddi-3.0.1/docs/db/ddl/ Files are not currently present in SOA-P distribution. For correct integration it has to be ensured that 1) Files are put in juddi_sql directory in jbossesb-registry.sar 2) Initial data are also provided in form of SQL script instead of XML 3) There will be a service that will initialize a database - create and fill 4) Schema tool will support this new way of configuration Look at jboss.esb for data-source configuration how to do it properly Link: Added: This issue related SOA-1917 setup xml provided, will provide a more standard setup in 5.0.1 Added as a known issue to 5.0.0: jUDDI v3 uses Hibernate to create its database. This is different to the other ESB components that use SQL scripts. This will be standardized in a future release. Link: Added: This issue depends JBESB-3319 ESB work has been done, will be in next merge. Support for jUDDI database creation is now in the ESB 4.7 branch and added to the schema tool with revision 5698 of:: schema-tool/build.xml schema-tool/juddi-service.xml (added) Commit message: SOA-1600 Change jUDDI database creation to standard and add to schema tool Verified in CR1 Release Note draft states: https://jira.jboss.org/jira/browse/SOA-1600 The jUDDI v3 database was created through the use of Hibernate. This was in contrast to the other ESB components, which used SQL scripts. The Schema tool has now been revised to support the creation of the jUDDI database. |