Bug 778093 (SOA-604)

Summary:	DB schema tool (jboss-as/tools/schema) provides workaround for inadvertent DB schema visibility for Oracle - should do the same for DB2
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Len DiMaggio <ldimaggi>
Component:	Tooling	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CP02
Target Milestone:	---
Target Release:	4.3 CP02
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-604
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	SOA-P CP02 CR2 build
Last Closed:	2009-08-14 19:42:24 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:
Embargoed:
Bug Depends On:	778120
Bug Blocks:

Description Len DiMaggio 2008-06-23 15:27:11 UTC

Date of First Response: 2009-07-30 09:23:04
project_key: SOA

The workaround to the user running the ESB server having visibility into DB schemas beyond its own - where the result is that the HILOSEQUENCES table to not created - is worked around in the schema tool template files for Oracle here:

/opt/CP02_CR2/jboss-soa-p-standalone.4.2.0/jboss-as/tools

[ldimaggi@ldimaggi tools]$ grep -r HILOSEQUENCES * | grep USERNAME
schema/oracle9i/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>
schema/oracle10g/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>

We'll need the same workaround for DB2 - when the schema tool is extended to support DB2.

Comment 1 Len DiMaggio 2008-06-23 15:27:27 UTC

Link: Added: This issue depends SOA-541

Comment 2 Len DiMaggio 2008-06-23 15:38:40 UTC

Link: Added: This issue related JBQA-1579

Comment 3 Julian Coleman 2009-01-14 14:07:01 UTC

Link: Removed: This issue depends SOA-541

Comment 4 Julian Coleman 2009-01-14 14:07:44 UTC

Link: Added: This issue depends SOA-630

Comment 5 Julian Coleman 2009-07-30 13:23:04 UTC

The current files on the 4.3 branch contain:
 
  :; grep -r USERN.*HILOSE .                    
  ./oracle9i/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>
  ./oracle10g/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>
  ./sybase/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>
  ./db2/template/uuid-jboss-service.xml:     <attribute name="TableName">@USERNAME@.HILOSEQUENCES</attribute>

So, no changes are required.

Comment 6 Len DiMaggio 2009-08-14 19:42:24 UTC

Verified fixed in 4.3 CP02 CR2

Comment 7 Dana Mison 2009-08-19 10:09:55 UTC

in regards to documenting this as resolved in the 4.3.CP02 release notes:

I have no idea what this is about, any pointers would be good ;-)