[jboss-jira] [JBoss JIRA] (WFLY-1269) single jdbc driver deployed inside ear takes name of ear

[Paul Alesius (JIRA)]

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

Paul Alesius edited comment on WFLY-1269 at 7/18/13 5:00 PM:
-------------------------------------------------------------

This doesn't work in Wildfly Alpha 3.
When deploying a jboss-ds.xml using <driver>myear.ear</dirver>, it worked in jboss as 7, but not anymore.

I've tried most combinations of myear.eardriver.jar myeardriverjar myeardriver.jar  etc.

I don't know if the driver is found in the ear, there's no indication of this even with debug logging on.

Also, it's unclear how the driver version format is to be specified when the maven version is for example <version>9.2-1003-jdbc4</version>

Specifying it as <driver>myear.earpostgresql.jar</div> would be ideal as there won't be different versions in that same jar
                
      was (Author: paul_alesius):
    This doesn't work in Wildfly Alpha 3.
When deploying a jboss-ds.xml using <driver>myear.ear</dirver>, it worked in jboss as 7, but not anymore.

I've tried most combinations of myear.eardriver.jar myeardriverjar myeardriver.jar  etc.

I don't know if the driver is found in the ear, there's no indication of this even with debug logging on.

Also, it's unclear how the driver version format is to be specified when the maven version is for example <version>9.2-1003-jdbc4</version>
                  
> single jdbc driver deployed inside ear takes name of ear
> --------------------------------------------------------
>
>                 Key: WFLY-1269
>                 URL: https://issues.jboss.org/browse/WFLY-1269
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: JCA
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Tom Eicher
>            Assignee: Stefano Maestri
>             Fix For: 8.0.0.Alpha1
>
>
> We need to always give service name for jdbdriver as 
> {code}
> deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion
> {code}
> even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names.
> Original description was:
> Including a JDBC driver, in this case PostgreSQL, in an ear like
> {code}
> myapp.ear:
> lib/postgresql-9.1-901.jdbc4.jar
> {code}
> does deploy the driver:
> {code}
> 23:37:28,118 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1)
> {code}
> however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected,
> but it's {{myapp_ear}}.
> (Seen in admin console, and this is the only value accepted in my -ds.xml file.)
> 1. JDBC driver service should pick name of innermost jar, not of containing ear
> 2. driver name (as to be used in datasource definition) should be logged with the log message above.

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