single jdbc driver deployed inside ear takes name of ear

We need to always give service name for jdbdriver as

deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion

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

myapp.ear:
lib/postgresql-9.1-901.jdbc4.jar

does deploy the driver:

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)

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.