]
Heiko Rupp commented on AS7-1164:
---------------------------------
So after discussion on irc:
[11:53:14] <+maeste> pilhuhn: you can't use the add command for a deployed
driver
[11:53:15] <+pilhuhn> (obviously)
[11:53:23] <+pilhuhn> it is not deployed
[11:53:30] ChanServ sets mode +v AndyTaylor
[11:53:38] <+maeste> pilhuhn: yup, but it isn't a module
[11:53:44] <+pilhuhn> at least not to /subystem=datasources/jdbc-driver
[11:53:52] <+maeste> pilhuhn: add is only for module loaded driversers
[12:02:48] <+maeste> pilhuhn: :read-children give the correct answer because the
only drivers present at domain level are module's one
[12:03:08] <+pilhuhn> and for standalone?
[12:03:18] <+maeste> pilhuhn: there is a specific operation installed-drivers-list
[12:03:40] <+maeste> pilhuhn: I said domain, I mean at profile level
[12:04:05] <+maeste> pilhuhn: if you use the installed-drivers-list you should see
all drivers
[12:04:16] <+maeste> pilhuhn: I'm seeing it righ now:
[12:04:31] <+maeste> pilhuhn: [standalone@localhost:9999 /]
/subsystem=datasources:installed-drivers-list
12:04:36] <+pilhuhn> so I can use such a driver that shows up at
"installed-drivers-list" -- even if it does not show up under
subsystem=datasources,jdbc-driver=* ?
[12:05:23] <+maeste> pilhuhn: yup
[12:05:25] <+maeste> pilhuhn: the operation have been done exactly for that
[12:05:27] <+maeste> pilhuhn: looking for the jira with brian's explanation
[12:05:29] <+maeste> pilhuhn: better than mine :)
[12:05:50] <+pilhuhn> So ss=ds/jdbc-drivers is basically useless for normal usage
[12:06:40] <+maeste> pilhuhn: yup if you have hot deployed drivers
[12:06:53] <+maeste> pilhuhn: it's fine only if you have only preloaded module
[12:06:59] ChanServ sets mode +v kkhan
[12:07:03] <+pilhuhn> even for the others ,as they all show up in
installed-drivers-lsit
[12:08:14] <+maeste> pilhuhn: here you have the discussion
add jdbc-driver : documentation incomplete or misleading
--------------------------------------------------------
Key: AS7-1164
URL:
https://issues.jboss.org/browse/AS7-1164
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.0.0.CR1
Reporter: Heiko Rupp
Assignee: Brian Stansberry
I want to add a jdbc driver to a profile. The driver has been uploaded to /deployment
[domain@localhost:9999 subsystem=datasources] pwd
/profile=default/subsystem=datasources
[domain@localhost:9999 subsystem=datasources]
./jdbc-driver=postgres9:add(driver-name=postgres9,deployment-name=postgresql-9.0-801.jdbc4.jar,driver-class-name=org.postgresql.Driver)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"Operation handler failed: java.util.NoSuchElementException: No child
'driver-module-name' exists"},
"rolled-back" => true
}
Documentation says:
[domain@localhost:9999 jdbc-driver=h2] :read-operation-description(name=add)
{
"outcome" => "success",
"result" => {
"operation-name" => "add",
"description" => "Adds a new JDBC driver service",
"attributes" => {
"driver-name" => {
"description" => "The symbolic name of this driver used
to reference it in the register",
"type" => STRING,
"required" => true
},
"deployment-name" => {
"description" => "The name of the deployment unit from
which the driver was loaded, if it was loaded from a deployment",
"type" => STRING
},
"driver-module-name" => {
"description" => "The name of the module from which the
driver was loaded, if it was loaded from the module path",
"type" => STRING
},
"module-slot" => {
"description" => "The slot of the module from which the
driver was loaded, if it was loaded from the module path",
"type" => STRING
},
"driver-class-name" => {
"description" => "The fully qualified class name of the
driver's implementation of java.sql.Driver",
"type" => STRING
},
"driver-major-version" => {
"description" => "The driver's major version
number",
"type" => INT
},
"driver-minor-version" => {
"description" => "The driver's minor version
number",
"type" => INT
},
"jdbc-compliant" => {
"description" => "Whether or not the driver is JDBC
compliant",
"type" => BOOLEAN
}
}
}
}
Here, only the driver-name is required.
For driver-module-name it says "if loaded from module", which I read as
"optional".
Obviously from above error message, this is not optional
--
This message is automatically generated by JIRA.
For more information on JIRA, see: