[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:comment-tabpanel&focusedCommentId=13095947#comment-13095947 ] 

Ramesh Reddy commented on TEIID-3609:
-------------------------------------

You can not do that. But you can add the connection definition to the existing resource-adapter definition. But you may have to restart the server at the end to activate the connection information you added.

The way the JCA susbsytem designed is not exactly same as the "jdbc" data source susbsystem, where the definition of the driver and connection management are two separate configuration entities and configuring (adding/deleteing) either of them does not require a server restart.

Where as in resource-adapter the definition of resource-adapter and connection information is single construct, if they both done at same time then you do not need to restart of the server before they become active, if you try adding one after another then you have to restart.

> 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)