Bug 781075 (SOA-3564)

Summary: When sequencing of Teiid Virtual model, the transformation (transform_selectSql) is not being found in the [transform:withSql] table when using jdbc interface
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Van Halbert <vhalbert>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2.0 GACC: jolee, rhauch
Target Milestone: ---   
Target Release: 5.3.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3564
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-11 04:54:58 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:
Bug Depends On:    
Bug Blocks: 781158    

Description Van Halbert 2011-11-08 15:05:48 UTC
project_key: SOA

Using the PartsVirtual.xmi model that used in the unit test for the teiid sequencer.

1)  attached is the test.log that prints when ModelSequencerTest.shouldSequencePartsSupplierVirtualRelationalModel test is run.   It shows the transformation thats defined for SupplierInfo

2)  published the model to a SOA server, used the jdbc.war, using jndi name java:ModeShapeDS, issue query: select * from [transform:withSql]         and it returned zero rows.

3)  used the FireFox json plugin to view Supplier info:  http://localhost:8080/modeshape-rest/eds/default/items/sequenced/teiid/models/teiid/PartsVirtual/SupplierInfo
(see attachment)  and its there:

{code}
"transform:selectSql": "SELECT PartSupplier_Oracle.SUPPLIER_PARTS.SUPPLIER_ID, PartSupplier_Oracle.SUPPLIER_PARTS.PART_ID, PartSupplier_Oracle.SUPPLIER_PARTS.QUANTITY, PartSupplier_Oracle.SUPPLIER_PARTS.SHIPPER_ID, PartsSupplier_SQLServer.SUPPLIER.SUPPLIER_NAME, PartsSupplier_SQLServer.SUPPLIER.SUPPLIER_STATUS, PartsSupplier_SQLServer.SUPPLIER.SUPPLIER_CITY, PartsSupplier_SQLServer.SUPPLIER.SUPPLIER_STATE FROM PartSupplier_Oracle.SUPPLIER_PARTS, PartsSupplier_SQLServer.SUPPLIER WHERE PartSupplier_Oracle.SUPPLIER_PARTS.SUPPLIER_ID = PartsSupplier_SQLServer.SUPPLIER.SUPPLIER_ID",
{code}

Not sure why its not coming thru the jdbc interface.

Comment 1 Van Halbert 2011-11-08 15:05:49 UTC
Link: Added: This issue Cloned from MODE-1296


Comment 2 Van Halbert 2011-11-08 15:07:42 UTC
Workflow: Removed: GIT Pull Request workflow  Added: jira
Release Notes Text: Added: When a vdb or model is checked into ModeShape for sequencing, the transformations will not be sequenced under the correct location and therefore, cannot be queried using the JDBC interface.
Security: Added: Public


Comment 3 Randall Hauch 2011-11-08 16:24:01 UTC
The changes from MODE-1296 were merged into the 'master' and '3.x' branches, but **NOT** on the branch used for SOA-P EDS 5.2. Please let us know when the change (74af30c336c) should be merged onto the '2.5.x' branch.

Comment 4 Van Halbert 2011-11-11 04:53:37 UTC
Git Pull Request: Removed: https://github.com/ModeShape/modeshape/pull/213 Added: https://github.com/ModeShape/modeshape/pull/213


Comment 5 Van Halbert 2011-11-11 04:54:58 UTC
ModeShape committed the fix to the 2.7 branch, which should be in the post 5.2 release.

Comment 6 Len DiMaggio 2011-11-15 17:52:50 UTC
Git Pull Request: Removed: https://github.com/ModeShape/modeshape/pull/213 Added: https://github.com/ModeShape/modeshape/pull/213


Comment 7 jolee 2011-12-09 15:14:52 UTC
Link: Added: This issue is a dependency of SOA-3656


Comment 8 jolee 2011-12-09 19:00:03 UTC
Randall,  please go ahead and merge into the 2.5.x branch.

Comment 9 jolee 2011-12-09 19:37:28 UTC
Link: Added: This issue Cloned to SOA-3659


Comment 10 jolee 2011-12-09 19:38:43 UTC
Link: Added: This issue is a dependency of SOA-3659


Comment 11 jolee 2011-12-09 19:38:52 UTC
Link: Removed: This issue Cloned to SOA-3659 


Comment 12 jolee 2011-12-09 19:39:08 UTC
Link: Removed: This issue is a dependency of SOA-3656 


Comment 13 Randall Hauch 2011-12-09 19:53:43 UTC
Merged the fix onto the '2.5.x' branch, as requested. At this point, the fix has been merged onto all active branches.