On Wed, Jun 15, 2011 at 17:58, Misty Stanley-Jones <misty@redhat.com> wrote:
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.
> On Wed, Jun 15, 2011 at 15:20, Dan Allen < dan.j.allen@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
>
>