[wildfly-dev] EE level java:comp/DefaultDataSource for WildFly 8...

[David M. Lloyd]

On 09/23/2013 10:04 AM, Jesper Pedersen wrote:
> On 09/23/2013 11:01 AM, Jaikiran Pai wrote:
>> On Monday 09 September 2013 09:53 PM, Scott Marlow wrote:
>>> I'm kind of caught on this requirement, since we already have a JPA
>>> level default datasource setting (for JPA container deployment).  I need
>>> to know if we are going to add a default datasource
>>> (java:comp/DefaultDataSource) setting to WildFly, so I can align with that.
>> I think we should add support for java:comp/DefaultDataSource since it's
>> required by spec. Furthermore, this isn't essentially just JPA thing
>> since such and injected/lookedup datasource could even be used in a
>> non-JPA application.
>
> I think the best solution is to add an element in the :ee: subsystem
> that points to a JNDI name defined in the :datasources: subsystem.
>
> We shouldn't make it a mandatory element though, since WildFly doesn't
> require a datasource to operate.

I updated the WFLY-2027 JIRA - I recall that it should be possible to 
configure this just by adding a single element to the naming subsystem 
(even though the context is EE-specific).

https://issues.jboss.org/browse/WFLY-2027#comment-12806620
-- 
- DML