----- Original Message -----
From: "Heiko Braun" <hbraun(a)redhat.com>
To: "Stefano Maestri" <smaestri(a)redhat.com>
Cc: jboss-as7-dev(a)lists.jboss.org
Sent: Friday, April 8, 2011 4:09:35 AM
Subject: Re: [jboss-as7-dev] problem creating datasources
On Apr 8, 2011, at 11:58 AM, Stefano Maestri wrote:
> The question is: does it make sense to have 2 different name for the
> same driver? Or we just need to have a better message to the user
> saying
> he can't do that because the same driver is already installed with a
> different name?
> I'm for the second option, but I'm open to the first one if there is
> a
> use case to do that.
> {
> "outcome" => "success",
> "result" => {
> "name" => "hypersonic",
> "driver" => "com.h2database.h2"
> },
> "compensating-operation" => undefined
> }
Thanks for the clarification, Stefano.
I don't really see a use case for the first example.
Guess it lead to the error because I was using the API in pretty dumb
way.
But if we go with the second option, why not drop simply the 'name'
property at all
if it's not used. Or is there a restriction on how the detyped api
works that requires a name?
When looking at the schema information, we mix in the module definition the pool
information for the data source, and the driver. What if I want to have two different
connection pools, against two different schemas in the same database, using the same
driver?
Andy
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev