8:58 a.m.
In AS7 upstream, how do I currently install a JDBC driver *as a module*
either via the CLI or the admin console? Looking at the admin console I
just see that it allows me a choose from a list of already installed
drivers while creating a datasource but doesn't allow me to add a new
driver. Is this feature planned for AS 7.0 CR1/Final? Or is the driver
installation supposed to happen outside of the admin console?
As for the CLI, I'm just trying to get a hang of the syntax. So far, I
haven't found a way to add a new JDBC driver (as a module) from the CLI.
Here's what I have tried so far:
[standalone@localhost:9999 /] /subsystem=datasources/jdbc-driver=new-one:add
{
"outcome" => "failed",
"failure-description" => [("java.util.NoSuchElementException"
=>
"No child 'driver-name' exists")]
}
I guess I'm using a wrong syntax here. Anyone knows how to go about
this? In the meantime, I'll go check the CLI syntax wiki.
P.S: By the way, I don't understand what that error message is trying to
convey to me. What does no child "driver-name" mean?
-Jaikiran
2 a.m.
On Jun 4, 2011, at 3:58 PM, Jaikiran Pai wrote:
In AS7 upstream, how do I currently install a JDBC driver *as a
module*
either via the CLI or the admin console? Looking at the admin console I
just see that it allows me a choose from a list of already installed
drivers while creating a datasource but doesn't allow me to add a new
driver. Is this feature planned for AS 7.0 CR1/Final? Or is the driver
installation supposed to happen outside of the admin console?
Simply deploy it and it will show up on the pull down list,
when creating a datasource.
Ike
2:09 a.m.
On Monday 06 June 2011 12:30 PM, Heiko Braun wrote:
On Jun 4, 2011, at 3:58 PM, Jaikiran Pai wrote:
> In AS7 upstream, how do I currently install a JDBC driver *as a module*
> either via the CLI or the admin console? Looking at the admin console I
> just see that it allows me a choose from a list of already installed
> drivers while creating a datasource but doesn't allow me to add a new
> driver. Is this feature planned for AS 7.0 CR1/Final? Or is the driver
> installation supposed to happen outside of the admin console?
Simply deploy it and it will show up on the pull down list,
when creating a datasource.
As a deployment, it's easy. But deploying it as a
module is more
involved and most of it is boilerplate
http://community.jboss.org/wiki/DataSourceConfigurationinAS7#Installing_a....
So I was thinking if we should simplify adding it as a module via admin
console (autogenerate the module.xml and other stuff based on the user
input) or even the CLI perhaps. Having said that, I don't know how many
users will be opting for deploying the JDBC driver as a module.
-Jaikiran
2:15 a.m.
On Jun 6, 2011, at 9:09 AM, Jaikiran Pai wrote:
> when creating a datasource.
As a deployment, it's easy. But deploying it as a module is more involved and most of
it is
boilerplatehttp://community.jboss.org/wiki/DataSourceConfigurationinAS7#I....
So I was thinking if we should simplify adding it as a module via admin console
(autogenerate the module.xml and other stuff based on the user input) or even the CLI
perhaps. Having said that, I don't know how many users will be opting for deploying
the JDBC driver as a module.
The question is: why would you chose a module configuration opposed to a deployment?
To be honest, I cannot tell the difference. It will probably have a different
scope/visibility, no?
Ike
9:02 a.m.
On 6/6/11 2:15 AM, Heiko Braun wrote:
On Jun 6, 2011, at 9:09 AM, Jaikiran Pai wrote:
>> when creating a datasource.
> As a deployment, it's easy. But deploying it as a module is more
> involved and most of it is
>
boilerplatehttp://community.jboss.org/wiki/DataSourceConfigurationinAS7#I....
> So I was thinking if we should simplify adding it as a module via
> admin console (autogenerate the module.xml and other stuff based on
> the user input) or even the CLI perhaps. Having said that, I don't
> know how many users will be opting for deploying the JDBC driver as a
> module.
The question is: why would you chose a module configuration opposed to a
deployment?
To be honest, I cannot tell the difference. It will probably have a
different scope/visibility, no?
This post on a separate thread explains the use case for using a module:
http://lists.jboss.org/pipermail/jboss-as7-dev/2011-June/002313.html
At this point the assumption is that modules are provisioned by the end
user as part of their process of install the AS on the system. That is,
the users copy the module to the modules/ dir. As Jason mentions above,
at some point we'd like to add capabilities to the management layer to
assist users with this. But it's not going to happen for 7.0 and isn't a
critical requirement for 7.1.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
11:15 a.m.
I think Jason comment about the "Gold Master" is a very good one. It's what
the vast majority of our customers do, so I think that the use case for having data
sources and their driver be a module will be more common than we may have thought before.
Andy
----- Original Message -----
From: "Brian Stansberry"
<brian.stansberry(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Monday, June 6, 2011 8:02:55 AM
Subject: Re: [jboss-as7-dev] How to install a JDBC driver as a module
via CLI or console?
On 6/6/11 2:15 AM, Heiko Braun wrote:
>
> On Jun 6, 2011, at 9:09 AM, Jaikiran Pai wrote:
>
>>> when creating a datasource.
>> As a deployment, it's easy. But deploying it as a module is more
>> involved and most of it is
>>
boilerplatehttp://community.jboss.org/wiki/DataSourceConfigurationinAS7#I....
>> So I was thinking if we should simplify adding it as a module via
>> admin console (autogenerate the module.xml and other stuff based
>> on
>> the user input) or even the CLI perhaps. Having said that, I don't
>> know how many users will be opting for deploying the JDBC driver
>> as a
>> module.
>
>
>
> The question is: why would you chose a module configuration opposed
> to a
> deployment?
> To be honest, I cannot tell the difference. It will probably have a
> different scope/visibility, no?
>
This post on a separate thread explains the use case for using a
module:
At this point the assumption is that modules are provisioned by the
end
user as part of their process of install the AS on the system. That
is,
the users copy the module to the modules/ dir. As Jason mentions
above,
at some point we'd like to add capabilities to the management layer
to
assist users with this. But it's not going to happen for 7.0 and
isn't a
critical requirement for 7.1.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
7:57 a.m.
I'm gonna look into adding drivers with the CLI after I'm done with
datasources.
On 06/06/2011 09:09 AM, Jaikiran Pai wrote:
On Monday 06 June 2011 12:30 PM, Heiko Braun wrote:
>
> On Jun 4, 2011, at 3:58 PM, Jaikiran Pai wrote:
>
>> In AS7 upstream, how do I currently install a JDBC driver *as a module*
>> either via the CLI or the admin console? Looking at the admin console I
>> just see that it allows me a choose from a list of already installed
>> drivers while creating a datasource but doesn't allow me to add a new
>> driver. Is this feature planned for AS 7.0 CR1/Final? Or is the driver
>> installation supposed to happen outside of the admin console?
>
>
>
> Simply deploy it and it will show up on the pull down list,
> when creating a datasource.
As a deployment, it's easy. But deploying it as a module is more
involved and most of it is boilerplate
http://community.jboss.org/wiki/DataSourceConfigurationinAS7#Installing_a....
So I was thinking if we should simplify adding it as a module via admin
console (autogenerate the module.xml and other stuff based on the user
input) or even the CLI perhaps. Having said that, I don't know how many
users will be opting for deploying the JDBC driver as a module.
-Jaikiran
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
4953
days inactive
4955
days old
6 comments
5 participants
participants (5)
-
Alexey Loubyansky -
Andrig Miller -
Brian Stansberry -
Heiko Braun -
Jaikiran Pai