I see that we ship a datasource out of the box and is available at java:/H2DS 12:59:31,816 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound JDBC Data-source [java:/H2DS] Would it be better to make it available at java:/DefaultDS? I am sure there are many quick start/example/demo applications out there which use java:DefaultDS for such simple examples. It would make it easier to use those examples in AS7, without having to change them, if we stick with the older name. Thoughts?

A couple of thoughts. 1) If we ship with one enabled out of the box I will leave to Jason to decide - why not save the boot time if we don't need it ? 2) We should try and limit (eliminate) subsystem/service dependency on an active database. 3) Having the name as 'DefaultDS' would leave the impression that the AS is using the database. I think a better route is to have the demos/samples/... just use the deployment api - through a script to the CLI f.ex. - to create the necessary resources and deploy their application.

>> A couple of thoughts. >> >> 1) If we ship with one enabled out of the box I will leave to Jason to >> decide - why not save the boot time if we don't need it ? >> >> 2) We should try and limit (eliminate) subsystem/service dependency on an >> active database. >> >> 3) Having the name as 'DefaultDS' would leave the impression that the AS >> is using the database. >> >> I think a better route is to have the demos/samples/... just use the >> deployment api - through a script to the CLI f.ex. - to create the >> necessary resources and deploy their application. > > or at least introduce something like what ds.xml files were used for ;) > You are pushing your luck, young man...

>>>> I think a better route is to have the demos/samples/... just use the >>>> deployment api - through a script to the CLI f.ex. - to create the >>>> necessary resources and deploy their application. >>> >>> or at least introduce something like what ds.xml files were used for ;) >>> >> >> You are pushing your luck, young man... > > Well, in my world its easier to copy files to a deployment directory or via managed api than > to support 3 different way to launch scripts * 2 different ways to handle Domain/Standalone. > > Just saying ;) Please don't hijack threads. Especially for topics that have already been beaten to death.

I have never really like the DefaultDS, as it tends to end up in production deployments, and people don't realize its just there for convenience. How hard is it to just change the name from DefaultDS, to H2DS? Andy ------------------------------------------------------------------------ *From: *"Jaikiran Pai" <jpai(a)redhat.com&gt; *To: *jboss-as7-dev(a)lists.jboss.org *Sent: *Wednesday, April 20, 2011 3:14:25 AM *Subject: *[jboss-as7-dev] Datasource name - DefaultDS instead of H2DS? I see that we ship a datasource out of the box and is available at java:/H2DS 12:59:31,816 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound JDBC Data-source [java:/H2DS] Would it be better to make it available at java:/DefaultDS? I am sure there are many quick start/example/demo applications out there which use java:DefaultDS for such simple examples. It would make it easier to use those examples in AS7, without having to change them, if we stick with the older name. Thoughts? -Jaikiran _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

And by "java:/TestDS" you of course mean "java:jboss/TestDS" right? :-) On 04/20/2011 10:10 AM, Stefano Maestri wrote: > Yup I'm agree. > I was on the other side of the river (as final user and consultant) > until last July and I can assure that 99% installations I've seen have > DefaultDS deployed in production, and customer always say:"we can't > remove it it's the Default database used by JBoss" > H2DS is a bit better, but if we are going to break the old DefaultDS > convention why don't just call it something like java:/TestDS ? > > S. > > On 04/20/2011 05:02 PM, Andrig Miller wrote: >> I have never really like the DefaultDS, as it tends to end up in >> production deployments, and people don't realize its just there for >> convenience. >> >> How hard is it to just change the name from DefaultDS, to H2DS? >> >> Andy >> >> ------------------------------------------------------------------------ >> >> *From: *"Jaikiran Pai&quot;&lt;jpai(a)redhat.com&gt; >> *To: *jboss-as7-dev(a)lists.jboss.org >> *Sent: *Wednesday, April 20, 2011 3:14:25 AM >> *Subject: *[jboss-as7-dev] Datasource name - DefaultDS instead of >> H2DS? >> >> I see that we ship a datasource out of the box and is available at >> java:/H2DS >> >> 12:59:31,816 INFO [org.jboss.as.connector.subsystems.datasources] >> (MSC service thread 1-4) Bound JDBC Data-source [java:/H2DS] >> >> Would it be better to make it available at java:/DefaultDS? I am >> sure there are many quick start/example/demo applications out >> there which use java:DefaultDS for such simple examples. It would >> make it easier to use those examples in AS7, without having to >> change them, if we stick with the older name. Thoughts? >> >> -Jaikiran >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On 4/20/11 10:10 AM, Stefano Maestri wrote: > Yup I'm agree. > I was on the other side of the river (as final user and consultant) > until last July and I can assure that 99% installations I've seen have > DefaultDS deployed in production, and customer always say:"we can't > remove it it's the Default database used by JBoss" > H2DS is a bit better, but if we are going to break the old DefaultDS > convention why don't just call it something like java:/TestDS ? That is really really scary.

Look at any wiki, or training we have on the subject... Sent from my iPhone On Apr 22, 2011, at 5:55 PM, Jim Tyrrell <jtyrrell(a)redhat.com&gt; wrote: >> On 4/20/11 10:10 AM, Stefano Maestri wrote: >>> Yup I'm agree. >>> I was on the other side of the river (as final user and consultant) >>> until last July and I can assure that 99% installations I've seen have >>> DefaultDS deployed in production, and customer always say:"we can't >>> remove it it's the Default database used by JBoss" >>> H2DS is a bit better, but if we are going to break the old DefaultDS >>> convention why don't just call it something like java:/TestDS ? >> >> That is really really scary. > > > How is the above scary, where is a good getting started guide letting them know what they should do to put this into production? How would you expect anything else if it is not documented clearly, and I am not saying if I look in 45 different places I might find something that says I can delete it. What I am talking about is clear getting started documentation around many different use cases. > >

The product docs are here: http://docs.redhat.com/docs/en-US/index.html Not very clear here: http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5... Also not clear here: http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5... Kevin's Cookbook is the cleanest info on this that I think we are shipping around the products, but to date this has not been documented in a way that mere mortal users could get, sorry. wiki pages, do we have a new product wiki that I am aware of.... ;) Jim Tyrrell Senior JBoss Solutions Architect Did you see RHT on CNBC's Mad Money? http://www.cnbc.com/id/39401056 On Apr 22, 2011, at 7:51 PM, Jason Greene wrote: > Look at any wiki, or training we have on the subject... > > Sent from my iPhone > > On Apr 22, 2011, at 5:55 PM, Jim Tyrrell <jtyrrell(a)redhat.com&gt; wrote: > >>> On 4/20/11 10:10 AM, Stefano Maestri wrote: >>>> Yup I'm agree. >>>> I was on the other side of the river (as final user and consultant) >>>> until last July and I can assure that 99% installations I've seen have >>>> DefaultDS deployed in production, and customer always say:"we can't >>>> remove it it's the Default database used by JBoss" >>>> H2DS is a bit better, but if we are going to break the old DefaultDS >>>> convention why don't just call it something like java:/TestDS ? >>> >>> That is really really scary. >> >> >> How is the above scary, where is a good getting started guide letting them know what they should do to put this into production? How would you expect anything else if it is not documented clearly, and I am not saying if I look in 45 different places I might find something that says I can delete it. What I am talking about is clear getting started documentation around many different use cases. >> >>