[wildfly-dev] datasource:installed-drivers-list()

[Stefano Maestri]

Yup you are right, but in standalone is different and this operation
give you also ones installed by deployments.
In domain this is not possible since deployments are local to single hosts.

regards
S.

On 05/15/2015 02:56 PM, Heiko Braun wrote:
> Ok, thanks.
> This leads me to two further questions:
>
> a) why does it need a separate operation? The same can be achieved with read-children-resources.
>
> b) what happened to the mechanism to detect drivers that are installed as deployments? iirc this particular operation used to show them in the past.
>
>
>
>> Am 15.05.2015 um 14:23 schrieb Stefano Maestri <smaestri at redhat.com>:
>>
>> Expected behavior is
>>
>>
>> c) any driver resource declared under subsystem=datasources/jdbc-driver=*
>>
>>
>>
>> regards
>> S.
>>
>>
>>
>>> On 05/15/2015 12:08 PM, Heiko Braun wrote:
>>> What’s the expected output of the installed-drivers-list() operation in the domain?  What drivers should it be listing?
>>>
>>> a) any driver:  no matter wether it’s a module or deployment 
>>> b) any driver installed as a module
>>> c) any driver resource declared under subsystem=datasources/jdbc-driver=*
>>> d) a combination of any of the above
>>>
>>>
>>> /Heiko
>>>
>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev