[teiid-issues] [JBoss JIRA] Resolved: (TEIID-1347) Configuration Update for Teiid Engine Should Look for compName Instead of Name

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-1347.
---------------------------------

    Resolution: Done


This was wrongly coded. There are more than one Socket Configuration in the profile. Granted JOPR only exposes the JDBC configuration, but there are MO for all the JDBC, Admin, ODBC configurations too. Since the update call can not tie to single configuration it was failing.

Also, the properties in this group are defined with flat scope, thus properties from JDBC can override ODBC vice versa. Added the scope names to each and every property based on the MO's name, such that they will not be misinterpreted anymore. 

Also there were few properties non existent, like "process name" and "active session count" these were removed.

Added few extra properties - Data Roles enable, JDBC enable, active plans allowed.

> Configuration Update for Teiid Engine Should Look for compName Instead of Name  
> --------------------------------------------------------------------------------
>
>                 Key: TEIID-1347
>                 URL: https://jira.jboss.org/browse/TEIID-1347
>             Project: Teiid
>          Issue Type: Bug
>          Components: Jopr Plugin
>            Reporter: Ted Jones
>            Assignee: Ramesh Reddy
>             Fix For: 7.1.1
>
>
> When updating properties of the Teiid engine in Admin Console I get an NPE. This is due to the service component name changing, which is a property that Teiid has no control over. The compName property of the the component is explicitly set on the component so the plugin code needs to look for that value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira