openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dick <>
Subject Re: OpenJPA without jta-data-source in persistence xml
Date Mon, 03 May 2010 18:38:57 GMT
Hi Pinaki,

Thanks for looking into this. I was hoping it'd be relatively
straight-forward to implement. I do have a couple of minor questions

1.) Is the jta-data-source needed in your example :

                <property name="openjpa.BrokerFactory" value="slice"/>
                <property name="openjpa.slice.Names"
                <property name="openjpa.slice.Master" value="slice1"/>
                <property name="openjpa.slice.slice1.ConnectionFactoryName"
                <property name="openjpa.slice.slice2.ConnectionFactoryName"
                <property name="openjpa.slice.slice3.ConnectionFactoryName"
                <property name="openjpa.TransactionMode" value="managed" />
               <property name="openjpa.ConnectionFactoryMode"
value="managed" />

It seems we could either omit the jta-data-source, or infer that it is the
master slice if it is present.  Maybe a better question is, what would
happen if the jta-data-source and the master slice were different?

2.) If the entity manager is JTA scoped, then openjpa.TransactionMode and
openjpa.ConnectionFactoryMode should already be set to managed. Is there
anything in slice that would require them to be set?



On Wed, Apr 28, 2010 at 4:58 PM, Pinaki Poddar <> wrote:

> Slice currently does not recognize configured JNDI-registered data sources.
> The only existing way is to configure each slice via an explicit connection
> url.
> Here is a proposal to allow better configuration in JEE.
> -----
> Pinaki
> --
> View this message in context:
> Sent from the OpenJPA Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message