[teiid-issues] [JBoss JIRA] (TEIID-3609) Teiid Connection import: driver field not populated for resource adapters

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-3609.
---------------------------------
      Assignee: Ramesh Reddy
    Resolution: Rejected


None of below configuration as is wrong, they all work, but it does change the default behavior with the tools.

The issue is a given "resource-adpater" does let you define multiple connection-definitions. However, every time you add or delete a connection-definition to the resource-adapater, the server needs to be restarted. That how EAP's JCA sub-system is designed.

Now, in Teiid it is very common to have different sources, adding and removing is quite a normal. However, restart each time is not accepted. So, the workaround that has been used is

- use empty resource-adapter definition as "driver" definition to enable data source template definition through Admin API

- Use a duplicated resource-definition with UNIQUE name and ONE connection-definition for every connection definition.

This way server does not need to be restarted when a connection definition is added to the resource-adapter. 

> Teiid Connection import: driver field not populated for resource adapters
> -------------------------------------------------------------------------
>
>                 Key: TEIID-3609
>                 URL: https://issues.jboss.org/browse/TEIID-3609
>             Project: Teiid
>          Issue Type: Bug
>            Reporter: Andrej Šmigala
>            Assignee: Ramesh Reddy
>
> When importing using Teiid Connection, the driver field is not populated for resource adapters when the pool name of the connection definition is the same as the id of the resource adapter itself. Except for the case that there is _another_ resource adapter defined for the same module _without_ any connection definitions.
> In other words, when the following is included in standalone.xml, the driver field is not populated
> {code:xml}
> <resource-adapter id="file">
>     <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
>     <transaction-support>NoTransaction</transaction-support>
>     <connection-definitions>
>         <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/file" enabled="true" pool-name="file">
>             <config-property name="ParentDirectory">
>                 /home/
>             </config-property>
>         </connection-definition>
>     </connection-definitions>
> </resource-adapter>
> {code}
> However, everything works as expected when the configuration is changed to this:
> {code:xml}
> <resource-adapter id="file">
>     <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
>     <transaction-support>NoTransaction</transaction-support>
>     <connection-definitions>
>         <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/fileDS" enabled="true" pool-name="fileDS">
>             <config-property name="ParentDirectory">
>                 /home/
>             </config-property>
>         </connection-definition>
>     </connection-definitions>
> </resource-adapter>
> {code}
> Or this:
> {code:xml}
> <resource-adapter id="file">
>     <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
> </resource-adapter>
> <resource-adapter id="fileDS">
>     <module slot="main" id="org.jboss.teiid.resource-adapter.file"/>
>     <transaction-support>NoTransaction</transaction-support>
>     <connection-definitions>
>         <connection-definition class-name="org.teiid.resource.adapter.file.FileManagedConnectionFactory" jndi-name="java:/fileDS" enabled="true" pool-name="fileDS">
>             <config-property name="ParentDirectory">
>                 /home/
>             </config-property>
>         </connection-definition>
>     </connection-definitions>
> </resource-adapter>
> {code}
> This might be related to TEIIDDES-1895 and is most likely the original cause of TEIIDDES-2563.
> Clicking Next in the import wizard when such a datasource is selected causes the same error as described in TEIIDDES-2563.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)