[
https://issues.jboss.org/browse/AS7-3347?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky resolved AS7-3347.
------------------------------------
Resolution: Won't Fix
I've also added tab-completion for driver-name argument in standalone mode, in the
case of domain, it's too complicated since the drivers are added per server but the
datasources are added per profile.
If there are other suggestions, please, let me know. I don't have anything else in
mind to add here.
JDBC drivers installed via deployment not shown in the management
model
-----------------------------------------------------------------------
Key: AS7-3347
URL:
https://issues.jboss.org/browse/AS7-3347
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
Labels: eap6_prd_req
Fix For: 7.1.2.Final
JDBC drivers installed via deployment are not shown in the management model. I am not
quite sure if this is intended or not but I see this as serious usability issue. How is
the user supposed to quess the driver name installed via deployment to be able to manage
data sources using this driver?
[standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver
h2
[standalone@localhost:9999 /] deploy /usr/share/java/postgresql-jdbc3.jar
[standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver
h2
[standalone@localhost:9999 /]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira