[jboss-jira] [JBoss JIRA] (AS7-6565) jdbc driver deployed inside ear takes name of ear

[jaikiran pai (JIRA)]

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

jaikiran pai commented on AS7-6565:
-----------------------------------

I don't think this is a bug. In fact, I think it's good to have the .ear name as part of the driver name. I even think there was a proper feature request for this. Consider a case where you deployed 2 different versions but with the same name, foo-driver.jar JDBC jar as part of 2 different EAR files. You want them to be unique and uniquely identifiable. So if I was packaging the driver jar as part of the EAR, I would find it right that the ear name is being used to identify the driver.

As for:
{quote}
2. driver name (as to be used in datasource definition) should be logged with the log message above.
{quote}
I think that's a reasonable enhancement. If not as part of that log message, maybe we should add a new log message which writes out the driver name. Of course if it isn't already being done.

I'll leave it to the JCA team to decide about this though. I'll set the right component of this JIRA so that it gets handled by the JCA team.

                
> jdbc driver deployed inside ear takes name of ear
> -------------------------------------------------
>
>                 Key: AS7-6565
>                 URL: https://issues.jboss.org/browse/AS7-6565
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.1.1.Final
>            Reporter: Tom Eicher
>
> 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