On Wed, Jun 15, 2011 at 15:20, Dan Allen < dan.j.allen(a)gmail.com > wrote: Can we include a sample datasource named jdbc/sample so that it's possible to deploy the same example application to JBoss AS and GlassFish without any other configuration? This is a constant headache for creating quickstart applications and we have the opportunity to close the gap. Here's the gap we've been juggling: JBoss AS < 7: java:/DefaultDS GlassFish 3: jdbc/__default and jdbc/sample

I know this seems trivial, but trust me, it makes a huge difference to help bring new users on board. They are forced to deal with datasources before they can learn anything else. -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://www.google.com/profiles/dan.j.allen#about http://mojavelinux.com http://mojavelinux.com/seaminaction _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

> On Wed, Jun 15, 2011 at 15:20, Dan Allen< dan.j.allen(a)gmail.com&gt; > wrote: > > > > Can we include a sample datasource named jdbc/sample so that it's > possible to deploy the same example application to JBoss AS and > GlassFish without any other configuration? This is a constant headache > for creating quickstart applications and we have the opportunity to > close the gap. > > > Here's the gap we've been juggling: > > > JBoss AS< 7: java:/DefaultDS > GlassFish 3: jdbc/__default and jdbc/sample > > In addition to the testing / migration points Dan makes, this actually has a docs/QE impact. It often comes up that customers think the name DefaultDS means something specific, and that they shouldn't change it. Since we absolutely don't want them using the sample datasource for production, I think calling it "sample" is a win all around. I think customers would be much less comfortable using the "sample" datasource in production than trying to use the "default" datasource in production. > I know this seems trivial, but trust me, it makes a huge difference to > help bring new users on board. They are forced to deal with > datasources before they can learn anything else. > > > -Dan > -- > > Dan Allen Principal Software Engineer, Red Hat | Author of Seam in > Action > Registered Linux User #231597 > > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > > > > -- > > Dan Allen Principal Software Engineer, Red Hat | Author of Seam in > Action > Registered Linux User #231597 > > > http://www.google.com/profiles/dan.j.allen#about > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev