[jboss-as7-dev] Locating JDBC drivers

[Heiko Braun]

Whatever we chose, here's the issue:
https://issues.jboss.org/browse/JBAS-9332

Ike


On Apr 15, 2011, at 3:33 PM, Jason T. Greene wrote:

> I think the best solution here is to have a management operation on a runtime node that returns the "available" drivers.
> 
> On 4/15/11 8:29 AM, John Bailey wrote:
>> Currently there is no way.  I think we will need update the
>> deployment based drive install in some way to make that available.
>> The problem with having the deployment add the drivers to the model
>> is you then have multiple ways to manage it.  You could undeploy to
>> remove or you could use a model operation to remove. This should be
>> ok as long as the deployment is smart enough to not update the model,
>> on undeploy, if the driver was removed by a model op.
>> 
>> Something we should think about from a architectural point of view is
>> whether or not we want deployments updating the model in this way.
>> 
>> John
>> 
>> On Apr 15, 2011, at 8:14 AM, Heiko Braun<hbraun at redhat.com>  wrote:
>> 
>>> 
>>> 
>>> 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.
>>> 
>>> 
>>> Ike
>>> 
>>> 
>>> 
>>> _______________________________________________ jboss-as7-dev
>>> mailing list jboss-as7-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> 
>> _______________________________________________ jboss-as7-dev mailing
>> list jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 
> 
> -- 
> Jason T. Greene
> JBoss, a division of Red Hat