I would consider it best practice that you have a way to separate what
database you run against and what database you test against.
Using -test.ds.xml is a way to achieve that in a way that works in all
cases without requiring property replacement magic doing development
Default data sources is one of the new features of Java EE 7 and I
its worth showcasing how apps can be simplified with that. I'll let
decide upon resource/time but its useful IMHO.
On Fri Oct 31 2014 at 6:01:34 AM Sebastian Łaskawiec <
> Hi Arun!
> Wildfly archetypes are created based on Quickstarts (just as Rafael
> mentioned here ).
> In case of *wildfly-**javaee7-webapp-blank-archetype* it is
> . Quickstarts are designed in such a way, that they can be
> deployed all
> together (this is why they need separate datasources).
> So, test-ds.xml is a design consequence of how Quickstarts are
> into archetypes. In my opinion we won't be able to get rid of it.
> Alternatively we could refactor all quickstarts to use default
> database -
> which might be pretty time consuming.
> Best regards
>  https://github.com/wildfly/quickstart/tree/master/kitchensink
> 2014-10-30 13:04 GMT+01:00 Arun Gupta <arun.gupta(a)gmail.com>:
>> For Java EE 7, a default data source is available if none is
>> in persistence.xml. In WildFly, this is mapped to ExampleDS already.
>> Does test-ds.xml create a new data source, or map to an existing one
>> On Thu, Oct 30, 2014 at 1:28 AM, Sebastian Łaskawiec
>> <slaskawi(a)redhat.com> wrote:
>>> I would like to volunteer for WFLY-4030 and a Quickstarts change:
>>> However I'm not sure about removing test-ds.xml. Maybe the point is
>>> show how to add DataSources bundled with the application?
>>> On the other hand if this is not the point - I think we should
>>> change it
>>> to ExampleDS.
>>> What's your opinion on that?
>>> Best regards
>>> On 10/29/2014 07:54 PM, Arun Gupta wrote:
>>>> - What is the purpose of test-ds.xml ? It contains:
>>>> This is anyway the default Java EE 7 data source in WildFly.
>>> wildfly-dev mailing list
>> wildfly-dev mailing list
> Sebastian Łaskawiec
wildfly-dev mailing list