[teiid-issues] [JBoss JIRA] (TEIID-2035) DeleteDataSource method on Admin API does not completely delete the Connection Factory

Ramesh Reddy (JIRA) jira-events at lists.jboss.org
Mon Aug 12 08:55:26 EDT 2013


    [ https://issues.jboss.org/browse/TEIID-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796233#comment-12796233 ] 

Ramesh Reddy commented on TEIID-2035:
-------------------------------------

Here is another variation of the script that is without the remove per the workaround suggested in the original JIRA. Note we are looking for a solution that does not require a restart.

{code} 
/subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS:add(jndi-name=java:/wsDS, class-name=org.teiid.resource.adapter.ws.WSManagedConnectionFactory, enabled=true, use-java-context=true)
/subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:add(value=http://foo.com)
/subsystem=resource-adapters/resource-adapter=ws:activate

/subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:remove
/subsystem=resource-adapters/resource-adapter=ws/connection-definitions=wsDS/config-properties=EndPoint:add(value=http://foo1.com)
{code}

I even tried the undefine-attribute instead of "remove" and "add" in last two lines of the script. 
                
> DeleteDataSource method on Admin API does not completely delete the Connection Factory
> --------------------------------------------------------------------------------------
>
>                 Key: TEIID-2035
>                 URL: https://issues.jboss.org/browse/TEIID-2035
>             Project: Teiid
>          Issue Type: Bug
>          Components: AdminApi
>    Affects Versions: 8.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>
> ConnectionFactory requires a two step creation process
> 1) create the resource-adaptor section
> 2) connection factory section
> The delete is removing the (2) and not (1). Thus any subsequent creates using the same name fails.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the teiid-issues mailing list