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.
Link: Added: This issue depends SOA-541
Link: Added: This issue related JBQA-1579
Link: Removed: This issue depends SOA-541
Link: Added: This issue depends SOA-630
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.
Verified fixed in 4.3 CP02 CR2
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 ;-)