Bug 780681 (SOA-3125)

Summary: Create Web Service fails if the model contains 2 schemas with the same tablenames underneath
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: dsteigne
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0 GA   
Target Milestone: ---   
Target Release: 5.3.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3125
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-15 19:27:35 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 dsteigne 2011-06-24 14:16:51 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007Ccyz
Workaround: Workaround Exists
Workaround Description: Multiple workarounds:
1. Generate the web service models individually (table level) instead of at the model level. This will allow you to make the output view and schemas unique in the "create web service" wizard.
2. Change all the table names in the second schema.  This may not be a viable solution though if the models contain numerous tables with the same name.
project_key: SOA

In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name.  Right-click > Modeling > Create Web Service fails:
"The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent."

The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView.
Comment 1 Van Halbert 2011-06-28 00:41:18 UTC 
Link: Added: This issue Cloned to SOA-3130
Comment 2 Ted Jones 2011-06-29 16:06:15 UTC 
Workaround Description: Removed: In order to keep both schemas underneath the same model all the tablenames in the second schema would need to be changed.  This isn't a viable solution though if the models contain numerous tables with the same name. Added: Multiple workarounds:
1. Generate the web service models individually (table level) instead of at the model level. This will allow you to make the output view and schemas unigue in the "create web service" wizard.
2. Change all the table names in the second schema.  This may not be a viable solution though if the models contain numerous tables with the same name.
Comment 3 Van Halbert 2011-06-29 19:03:31 UTC 
TeiidDesigner has targeted this fix for 7.5, but not sure when that branch will get release.
Comment 4 Ted Jones 2011-07-01 13:44:07 UTC 
Workaround Description: Removed: Multiple workarounds:
1. Generate the web service models individually (table level) instead of at the model level. This will allow you to make the output view and schemas unigue in the "create web service" wizard.
2. Change all the table names in the second schema.  This may not be a viable solution though if the models contain numerous tables with the same name. Added: Multiple workarounds:
1. Generate the web service models individually (table level) instead of at the model level. This will allow you to make the output view and schemas unique in the "create web service" wizard.
2. Change all the table names in the second schema.  This may not be a viable solution though if the models contain numerous tables with the same name.
Comment 5 Ted Jones 2011-07-01 15:15:46 UTC 
Link: Added: This issue depends TEIIDDES-968
Comment 6 Ted Jones 2011-07-01 15:17:00 UTC 
TEIIDDES-968 will allow the user to import tables with fully qualified names (including schema) which will allow the user to create web services for models that have schemas with duplicate table names.
Comment 7 Ted Jones 2011-07-15 19:27:35 UTC 
Release Notes Text: Added: This is resolved with the changes made by TEIIDDES-968