Bug 874669 - Upgrade to juddi 3.1.4
Summary: Upgrade to juddi 3.1.4
Keywords:
Status: ON_QA
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: tcunning
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 15:46 UTC by tcunning
Modified: 2018-03-23 21:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
It is desired that integration with jUDDI be upgraded for jUDDI version 3.1.4.
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
jUDDI database DDL upgrade statements (60.65 KB, text/plain)
2012-11-20 17:46 UTC, tcunning
no flags Details


Links
System ID Priority Status Summary Last Updated
JBoss Issue Tracker JBESB-3885 Major Closed Upgrade to jUDDI 3.1.4 2015-12-09 12:14:35 UTC
Red Hat Bugzilla 873821 None None None 2012-11-08 15:48:45 UTC

Description tcunning 2012-11-08 15:46:29 UTC
Description of problem:
Need to upgrade jUDDI to version 3.1.4

Comment 1 tcunning 2012-11-08 15:50:53 UTC
Need to create a jUDDI 3.1.4 for the linked issue and incorporate it.

Comment 2 tcunning 2012-11-20 17:46:04 UTC
Created attachment 648690 [details]
jUDDI database DDL upgrade statements

Comment 3 tcunning 2012-11-20 17:48:39 UTC
Moving to jUDDI 3.1.4 will require some changes to the schema scripts.     There are a number of create table statements, and a number of alter table statements (adding indices).     I've attached the patch file which shows the differences in the DDL for new installs - I think these will have to be added to the changes which are applied to existing installs.

Comment 4 JBoss JIRA Server 2012-12-03 17:50:52 UTC
Tom Cunningham <tcunning@redhat.com> updated the status of jira JBESB-3885 to Resolved

Comment 5 JBoss JIRA Server 2012-12-03 17:50:56 UTC
Tom Cunningham <tcunning@redhat.com> updated the status of jira JBESB-3885 to Closed


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