[jboss-jira] [JBoss JIRA] Commented: (AS7-328) Provide an operation to retrieve JDBC drivers that are installed as deployments

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on AS7-328:
--------------------------------------

We discussed on email; recapturing here. This works:

[localhost:9999 /] /host=local/server=server-one/subsystem=datasources:read-attribute(name=installed-drivers)
{
    "outcome" => "success",
    "result" => [{
        "deployment-name" => undefined,
        "module-name" => "com.h2database.h2",
        "module-slot" => "main",
        "driver-class" => "org.h2.Driver",
        "major-version" => 1,
        "minor-version" => 2,
        "jdbc-compliant" => true
    }],
    "compensating-operation" => undefined
}

This doesn't:

[localhost:9999 /] /profile=default/subsystem=datasources:read-attribute(name=installed-drivers)             
{
    "outcome" => "success",
    "result" => undefined,
    "compensating-operation" => undefined
}


Problem is this attribute is read from runtime state in a server; state which does not exist on the domain controller. It depends on runtime state in a server because if a driver is in a deployment we have no idea until it is deployed; i.e. until it goes through the deployers which only exist on the server.

The attribute shouldn't even be visible at the /profile=default/subsystem=datasources level. I'll think about how to make that happen.

> Provide an operation to retrieve JDBC drivers that are installed as deployments
> -------------------------------------------------------------------------------
>
>                 Key: AS7-328
>                 URL: https://issues.jboss.org/browse/AS7-328
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>             Fix For: 7.0.0.Beta4
>
>
> I managed to deploy JDBC drivers through the HTTP API.
> Creating datasources works as well. The remaining question is:
> How to I locate the JDBC drives that are installed as a deployment?
> They don't show up under /subsystem=datasources/jdbc-driver=*
> In order to create the Datasource I need to provide a list of available drives to the user.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira