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

[SBS JIRA Integration (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SBS JIRA Integration updated WFLY-1269:
---------------------------------------

    Forum Reference: https://community.jboss.org/message/799490#799490, https://community.jboss.org/message/871504#871504  (was: https://community.jboss.org/message/799490#799490)


> 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
>      Security Level: Public(Everyone can see) 
>          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 was sent by Atlassian JIRA
(v6.2.3#6260)