[jboss-jira] [JBoss JIRA] (WFLY-7973) WildFlyDataSource needs implementation of isWrapperFor method
Ivo Studensky (JIRA)
issues at jboss.org
Fri Jan 27 04:07:00 EST 2017
[ https://issues.jboss.org/browse/WFLY-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13354250#comment-13354250 ]
Ivo Studensky commented on WFLY-7973:
-------------------------------------
I am really not sure the attached reproducer is valid. {{org.jboss.as.connector.subsystems.datasources.WildFlyDataSource}} you get from lookup does not implement XADataSource directly. It is a wrapper with {{unwrap}} method unsupported, i.e. {{isWrapperFor}} should always return {{false}}, see javadoc for {{java.sql.Wrapper}}.
Moreover, I can't see any way how to determine from {{delegate}} WildFlyDataSource consist of if the proxy represents an XA datasource or non-XA datasource. The {{delegate}} is in fact {{org.jboss.jca.adapters.jdbc.WrapperDataSource}} which does not seem to contain any information if it belongs to XA or non-XA datasource. It neither contains any XA/non-XA datasource instance that can be returned from {{JBossWrapper.getWrappedObject}}.
I recall similar questions from the past, I will try to look around for any forum post related to this.
> WildFlyDataSource needs implementation of isWrapperFor method
> -------------------------------------------------------------
>
> Key: WFLY-7973
> URL: https://issues.jboss.org/browse/WFLY-7973
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.1.0.Final
> Reporter: Johnathon Lee
> Assignee: Flavia Rainone
>
> inability to determine datasource vs xa-datasource after JNDI lookup.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list