Hi, Any conclusion on the AS 7 default datasource name setup ? Currently its H2DS which means *zero* existing examples deploy even if they could and *all* examples and docs have to be ammended/commented that you have to configure the datasources your self (which is currently not very well documented). Any chance we can get DefaultDS bound by default by Final to reduce the amount of "gotchas" users moving from existing AS to the new ? /max http://about.me/maxandersen _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On Monday, June 13, 2011 08:54:19 AM Max Rydahl Andersen wrote: > Any conclusion on the AS 7 default datasource name setup ? > > Currently its H2DS which means *zero* existing examples deploy even if they > could and *all* examples and docs have to be ammended/commented that you > have to configure the datasources your self (which is currently not very > well documented). > > Any chance we can get DefaultDS bound by default by Final to reduce the > amount of "gotchas" users moving from existing AS to the new ? I'm against renaming it "DefaultDS" - as it signals that the application server requires a datasource to work.

The only reason we have a H2DS deployed currently is because the demos uses it. As to documentation it'll be fixed before Final. However, I'll leave it to Jason to decide on the matter. Best regards, Jesper _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On Monday, June 13, 2011 10:00:07 AM Brian Stansberry wrote: > Ins't the binding supposed to be under java:jboss/ anyway? (Forgive me; > I haven't been following the details on this stuff, so could be off base.) > > If so, it would be java:jboss/DefaultDS which breaks old stuff anyway; > might as well use java:jboss/H2DS. Or java:jboss/datasources/H2DS :) Stuart has some patches to align JNDI resources in the tree... I don't know if he will push them for 7.0 though.

>>> Any chance we can get DefaultDS bound by default by Final to reduce the >>> amount of "gotchas" users moving from existing AS to the new ? >> >> I'm against renaming it "DefaultDS" - as it signals that the application >> server requires a datasource to work. > > Ins't the binding supposed to be under java:jboss/ anyway? (Forgive me; > I haven't been following the details on this stuff, so could be off base.) > > If so, it would be java:jboss/DefaultDS which breaks old stuff anyway; > might as well use java:jboss/H2DS. If the binding will break anyway and Jesper thinks defaultDS means it signals AS requires a datasource to work how about creating a default datasource bound to ExampleDS ? I really don't like H2DS since its named to a specific database type/name. Having a dedicated Example datasource would make everyone equally happy or equally displeased dependent on your POV :) Note, the reason I raise this is that its a major annoyance for docs/usability wise and would be great to have something fairly clean from AS 7 Final.

> Just my 2 cents, but that makes sense to me. AIUI the only issue was not > using a name that implies the app server itself needs the datasource. > ExampleDS is actually better in that sense. I'm ok with java:jboss/datasources/ExampleDS too.

On 6/22/11 12:44 PM, Max Rydahl Andersen wrote: >>> Just my 2 cents, but that makes sense to me. AIUI the only issue was not >>> using a name that implies the app server itself needs the datasource. >>> ExampleDS is actually better in that sense. >> >> I'm ok with java:jboss/datasources/ExampleDS too. > > > What is the status on this one ? > > Master still says H2DS - is it a matter of just renaming it in standlone.xml (and others) or was there more things that needed doing ? > > If its just the rename's I can do that pullrequest pretty quickly - if its more..would need a little help. > I'd thought there was a patch for this that I merged, but I must be dreaming it. I'll look through the old history. The one I'm thinking of was more than a simple tweak to standalone.xml.

On 6/22/11 12:44 PM, Max Rydahl Andersen wrote: >>> Just my 2 cents, but that makes sense to me. AIUI the only issue was not >>> using a name that implies the app server itself needs the datasource. >>> ExampleDS is actually better in that sense. >> >> I'm ok with java:jboss/datasources/ExampleDS too. > > > What is the status on this one ? > > Master still says H2DS - is it a matter of just renaming it in standlone.xml (and others) or was there more things that needed doing ? > > If its just the rename's I can do that pullrequest pretty quickly - if its more..would need a little help. > I'd thought there was a patch for this that I merged, but I must be dreaming it. I'll look through the old history. The one I'm thinking of was more than a simple tweak to standalone.xml. -- Brian Stansberry Principal Software Engineer JBoss by Red Hat

AS7-975 has been postponed till 7.1.0.Alpha1 Is it really intentional? That means that each of {6, 7, 7.1} releases will have a different name for the built-in DS.

On 06/22/2011 08:06 PM, Max Rydahl Andersen wrote: > https://issues.jboss.org/browse/AS7-975 is marked as closed but i'm not seeing those changes ? > > And I see http://lists.jboss.org/pipermail/jbossas-pull-requests/2011-June/000940.html but > https://github.com/maeste/jboss-as/tree/AS7-975 does not exist anymore. > > Hope that helps ;) > > /max > > On Jun 22, 2011, at 19:47, Brian Stansberry wrote: > >> On 6/22/11 12:44 PM, Max Rydahl Andersen wrote: >>>>> Just my 2 cents, but that makes sense to me. AIUI the only issue was not >>>>> using a name that implies the app server itself needs the datasource. >>>>> ExampleDS is actually better in that sense. >>>> I'm ok with java:jboss/datasources/ExampleDS too. >>> >>> What is the status on this one ? >>> >>> Master still says H2DS - is it a matter of just renaming it in standlone.xml (and others) or was there more things that needed doing ? >>> >>> If its just the rename's I can do that pullrequest pretty quickly - if its more..would need a little help. >>> >> I'd thought there was a patch for this that I merged, but I must be dreaming it. I'll look through the old history. >> >> The one I'm thinking of was more than a simple tweak to standalone.xml. >> >> >> -- >> Brian Stansberry >> Principal Software Engineer >> JBoss by Red Hat > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On Mon, Jun 13, 2011 at 10:20 AM, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: If the binding will break anyway and Jesper thinks defaultDS means it signals AS requires a datasource to work how about creating a default datasource bound to ExampleDS ? I really don't like H2DS since its named to a specific database type/name. Don't you need to know which database/dialect you're using in order for hibernate to function properly anyway? In which case this might actually be *useful* information?

Good to know. I will remove the dialect from Forge.

On Mon, Jun 13, 2011 at 11:48 AM, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > On Mon, Jun 13, 2011 at 10:20 AM, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > If the binding will break anyway and Jesper thinks defaultDS means it signals AS requires > a datasource to work how about creating a default datasource bound to ExampleDS ? > > I really don't like H2DS since its named to a specific database type/name. > > Don't you need to know which database/dialect you're using in order for hibernate to function properly anyway? In which case this might actually be *useful* information? No, hibernate just autodetects by querying the database what is running on the "other" side. /max http://about.me/maxandersen -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"

It is perfectly valid to bind to "java:/DefaultDS", just a bit ugly.

On 06/13/2011 09:00 AM, Brian Stansberry wrote: > Ins't the binding supposed to be under java:jboss/ anyway? (Forgive me; > I haven't been following the details on this stuff, so could be off base.) Binding to "java:/DefaultDS" should be exactly equivalent (according to the rules set forth earlier) to "java:jboss/root/DefaultDS". As in the former is an alias for the latter.