Bug 779853 (SOA-2213) - schema tool cannot be used more than once
Summary: schema tool cannot be used more than once
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2213
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-09 14:42 UTC by Brad Maxwell
Modified: 2011-02-03 08:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-31 04:42:20 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2213 0 Blocker Closed schema tool cannot be used more than once 2012-07-19 07:27:57 UTC

Description Brad Maxwell 2010-08-09 14:42:51 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
Complexity: Low
Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/1002453
project_key: SOA

Ran schema changing script to change to oracle.  Then ran script again to change to postgres.

The script .  SOA comes configured with HSQL, if you run the script it will rename the *-ds.xml to *-ds.xml.org.  If you run the script again and change it to a different database, it leaves a lot of stuff behind.

1) leaves old *-ds.xml in deploy (for example oracle-ds.xml, unlike the other files, it doesn't rename it to .org)

2) leaves deploy/messaging/*persistence* (it similar to the datasource, it doesn't rename this one, so when you start you get errors about duplicates)

3) juddi_config/META-INF/persistence.xml
- It didn't change the hibernate.dialect to the new database
<property name="hibernate.dialect"
value="org.hibernate.dialect.PostgreSQLDialect" />

4) /deploy/jbossesb.esb/jbossesb-service.xml - it didn't update the message-store-sql to the new value
<attribute name="SqlFiles">
   message-store-sql/postgresql/create_database.sql

5)  jbossesb-registry.sar/juddi_config/META-INF/persistence.xml - it didn't update the hibernate dialect

6) deploy/uuid-key-generator.sar/META-INF/jboss-service.xml
- it left this somehow, this was when I had oracle config switching to postgres, I had to remove scott.
  <attribute name="TableName">scott.HILOSEQUENCES</attribute>

Comment 1 Julian Coleman 2010-09-09 11:12:56 UTC
The schema tool does not currently support being run more than once to change
to a different database.

Comment 2 Anne-Louise Tangring 2010-09-10 18:42:08 UTC
We may consider a schema tool that has capabilities like this for the future. For now, we need to document that the intent of the tool is to do a one time set, initial set up. This can be documented in the guide or maybe in a Readme.

Comment 3 Anne-Louise Tangring 2010-12-06 16:36:58 UTC
We need to clearly document that the schema tool can only be run once. There was never an intent for it to be run more than once. 

Comment 4 Dana Mison 2010-12-20 04:21:20 UTC
Labels: Removed: schema soa tool Added: ESB_Administrator_Guide Getting_Started_Guide schema soa tool


Comment 5 Dana Mison 2010-12-20 04:27:09 UTC
The ESB Administrators Guide explicity states that this tool can be run multiple times so long as there have been no other configuration changes to this file.

This needs to be removed and add the warning that it can only be run once.

Comment 6 Dana Mison 2010-12-20 04:27:09 UTC
Labels: Removed: ESB_Administrator_Guide Getting_Started_Guide schema soa tool Added: ESB_Administrator_Guide schema soa tool
Complexity: Added: Medium
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]


Comment 7 Dana Mison 2010-12-20 04:28:17 UTC
Complexity: Removed: Medium Added: Low


Comment 9 Dana Mison 2011-01-05 00:12:19 UTC
Writer: Added: Darrin


Comment 10 Dana Mison 2011-01-25 07:17:50 UTC
can you update the ESB Admin Guide with this please ?

Comment 11 David Le Sage 2011-01-31 04:42:20 UTC
Release Notes Text: Added: I have added this warning. I will add it to the project doc at the next merge.


Comment 12 Dana Mison 2011-02-03 08:28:55 UTC
Release Notes Text: Removed: I have added this warning. I will add it to the project doc at the next merge. 


Comment 13 Dana Mison 2011-02-03 08:29:16 UTC
Release Notes Docs Status: Added: Not Required



Note You need to log in before you can comment on or make changes to this bug.