9:54 a.m.
[
https://issues.jboss.org/browse/TEIID-3609?page=com.atlassian.jira.plugin...
]
Barry LaFond commented on TEIID-3609:
-------------------------------------
Teiid Designer has a forked version of the AdminFactoryImpl. The method that's
removing the resource-adapter, and hence not finding any driver/properties in Designer is
in question. getResourceAdapterNames() is used to return property sets for deployed Data
Sources. If user configures a resource adapter to use a pool name/JNDI name which is one
of the names of the resource-adapters, it'll remove the name and hence not return any
driver properties.
{code}
// :read-children-names(child-type=deployment)
private Set<String> getResourceAdapterNames() throws AdminException {
Set<String> templates = getDeployedResourceAdaptorNames();
templates.addAll(getInstalledResourceAdaptorNames());
//AS-4776 HACK - BEGIN
Map<String, String> connFactoryMap = getConnectionFactoryNames();
for (String key:connFactoryMap.keySet()) {
templates.remove(key);
}
//AS-4776 HACK - END
return templates;
}
{code}
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
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)
3900
days inactive
3900
days old
0 comments
1 participants
participants (1)
-
Barry LaFond (JIRA)