[teiid-issues] [JBoss JIRA] (TEIID-1832) Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model

[Ramesh Reddy (Resolved) (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy resolved TEIID-1832.
---------------------------------

    Resolution: Partially Completed

    
> Change to source model connection through AdminApi using assignToModel() does not reflect in jdbc queries to that source model
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEIID-1832
>                 URL: https://issues.jboss.org/browse/TEIID-1832
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi
>    Affects Versions: 7.5
>         Environment: Windows server 2008 R2, JBoss 5.1
>            Reporter: Farrukh Ihtisham
>            Assignee: Ramesh Reddy
>             Fix For: 7.6
>
>
> When source model's connection is changed using following adminapi code;
> AdminFactory adminFactory = AdminFactory.getInstance();
> Admin admin = adminFactory.createAdmin("admin", "admin".toCharArray(), "mms://localhost:31443"); 
> admin.assignToModel("Sample", 1, "SQLSourceA", "SQLSourceA", "sqlserver", "SQLSourceA_2");
> Any jdbc query result would still be from the old data source. However when verified using following adminapi code;
> VDB vdb = admin.getVDB("sample", 1);
> Model m = vdb.getModel("SQLSourceA");
> String jndiName = m.getSourceConnectionJndiName("SQLSourceA");
> The jndiName shows that the connection is successfully updated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira