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

[Tom Eicher (JIRA)]

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

Tom Eicher edited comment on AS7-6565 at 2/26/13 5:32 AM:
----------------------------------------------------------

Obviously, when the runtime name changed, and thus the expected {{<driver>}}, some code will break.
That is not necessarily a bug. Something for the release notes and/or the migration guide.
Everybody is waiting for the 2) of course, so that people may know they have the (now) wrong driver name...
                
      was (Author: tomeicher):
    Obviously, when the runtime name changed, and thus the expected {code}<driver>{code}, some code will break.
That is not necessarily a bug. Something for the release notes and/or the migration guide.
Everybody is waiting for the 2) of course, so that people may know they have the (now) wrong driver name...
                  
> single 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: Feature Request
>          Components: JCA
>    Affects Versions: 7.1.1.Final, 8.0.0.Alpha1
>            Reporter: Tom Eicher
>            Assignee: Stefano Maestri
>
> 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