[jboss-jira] [JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

[ted won (JIRA)]

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

ted won commented on JBJCA-1320:
--------------------------------

Yes, it's right, however, some cases there is no need to specify <connection-property>, now it occurs migration error to EAP 7.
WFLY-6198 will give a warning for this like below after merging this. :)
{code}
18:46:36,350 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
18:46:36,398 WARN [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-6) WFLYJCA0098: The datasource MySqlDS is using the driver datasource class "com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource", only connection-properties are used for configuration.
18:46:36,440 INFO [stdout] (MSC service thread 1-6) dataSourceClass=com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
18:46:36,444 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/MySqlDS]
{code}

> Unable to create JDBC local datasource without properties on JBoss EAP 7
> ------------------------------------------------------------------------
>
>                 Key: JBJCA-1320
>                 URL: https://issues.jboss.org/browse/JBJCA-1320
>             Project: IronJacamar
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: WildFly/IronJacamar 1.3.3.Final
>         Environment: JBoss EAP 7.0.0
>            Reporter: ted won
>            Assignee: ted won
>            Priority: Minor
>         Attachments: com.msql.tar.gz
>
>
> It should display warning message than throwing error as [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198].
> It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 to JBoss EAP 7 or creating non-XA datasource for using local transactions in JBoss EAP 7.
> In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but not EAP 7.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)