There's no maintenance branches in aries, so if the change (when/if accepted) requires a major version, that simply means the next release will be a major upgrade for jpa/container.
2014-09-26 14:12 GMT+02:00 Christian Schneider <[email protected]>: > On 26.09.2014 13:31, Guillaume Nodet wrote: > > >>> 4. Introduce a switch to decide if DataSource or XADataSource >>> should be created >>> >>> Apart from that I would like to introduce a switch that already allows to >>> use a managed transactional DataSource right now. So with this switch (in >>> persistence.xml ?) the user could choose if he wants to create the >>> DataSource from the DataSourceFactory using createDataSource() even in >>> JTA >>> mode or use createXADataSource() and let aries jpa do the wrapping. >>> >>> >>> I don't think it makes sense if #3 is done, right ? >> > If we can do 3 now then 4 makes no sense. If we do 3 on the next major > version then we should do 4 now to provide a compatible upgrade path. > > > Christian > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > >
