Yes, the proposal is to provide a
public class ConfigurableDataSourceimplements DataSource and a public class ConfigurableXaDataSource extends ConfigurableDataSource implements XaDataSource The reason for splitting those is that some containers do a instanceof XaDataSource to automatically detect JTA support. So we better keep it explicit, wdyt? LieGrue, strub ----- Original Message ----- > From: Jason Porter <[email protected]> > To: [email protected]; Mark Struberg <[email protected]> > Cc: > Sent: Monday, June 11, 2012 6:25 PM > Subject: Re: [DISCUSS] JPA ConfigurableDataSource > >T his implements DataSource (and maybe XaDataSource)? > > On Mon, Jun 11, 2012 at 2:34 AM, Mark Struberg <[email protected]> wrote: > >> Hi! >> >> We had some discussion about the ConfigurableDataSource [1] already. >> >> The old discussion can be found here [2] >> >> I now started porting over the stuff I did in CODI. >> In a second step I'll extend the functionality to provide support for >> XaDataSource. >> >> LieGrue, >> strub >> >> [1] >> > https://cwiki.apache.org/EXTCDI/jpa-usage.html#JPAUsage-ConfigurableDataSource%28sincev1.0.2%29 >> [2] http://markmail.org/thread/akm5qpnvzpzbqjsq >> > > > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > Author of Seam Catch - Next Generation Java Exception Handling > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net, pgp.mit.edu >
