[wildfly-dev] Java EE 7 and WildFly

[Scott Marlow]

I think that @DataSourceDefinition could work portably someday (JPA 
needs the two phase bootstrap and persistence providers to make some 
changes).

Probably best not to bring up what is wrong with @DataSourceDefinition 
in this thread (deserves its own thread).

On 10/28/2013 11:41 AM, Arun Gupta wrote:
> This is independent of @DataSourceDefinition. Moreover this is a spec
> compliance issue.
>
> Trying to understand what is the issue in adding a default data source ?
>
> Arun
>
> On Mon, Oct 28, 2013 at 3:27 AM, Jesper Pedersen
> <jesper.pedersen at jboss.org> wrote:
>> On 10/28/2013 06:24 AM, Arun Gupta wrote:
>>> Java EE 7 require a default data source to be available so there
>>> should be no need to configure an additional resource. Will be adding
>>> my feedback on:
>>>
>>> https://issues.jboss.org/browse/WFLY-2027
>>>
>>
>> WildFly doesn't require a datasource to operate, so which datasource is
>> the "default" is specified by the user in the configuration (:ee:).
>>
>> The configuration identifies a datasource controlled by the
>> :datasources: subsystem in order to have a working datasources instead
>> of the @DataSourceDefinition mess.
>>
>> Subsystems can choose to have local overrides if they want.
>>
>> Best regards,
>>    Jesper
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
>