Yes please since the example does not work
On Wed, Mar 6, 2013 at 9:42 AM, lb <[email protected]> wrote: > Should we open a JIRA? > > > On Wednesday, March 6, 2013, Dan Tran wrote: >> >> same here >> >> On Tue, Mar 5, 2013 at 11:40 PM, Bengt Rodehav <[email protected]> wrote: >> > I have been looking for the exact same thing. Putting these properties >> > in >> > persistence.xml is, in my opininon, broken since they will, as you point >> > out, be hard coded. >> > >> > I would really appreciate a way to use the config admin for this. >> > >> > /Bengt >> > >> > >> > 2013/3/6 lb <[email protected]> >> >> >> >> Yes I know but then the properties are hardcoded and to change them I >> >> have >> >> to redeploy a bundle. Would be nice to be able to configure the >> >> persistence >> >> unit at runtime. In the aries jpa project page there is an example for >> >> an >> >> extended persistence context but it does not work. >> >> >> >> >> >> On Tuesday, March 5, 2013, Christoph Gritschenberger wrote: >> >>> >> >>> You can put those in your persistence.xml >> >>> >> >>> kind regards, >> >>> christoph >> >>> >> >>> On 2013-03-05 17:49, lb wrote: >> >>>> >> >>>> Hi, >> >>>> >> >>>> I would like to know, whatever it is possible to initialize a >> >>>> persistence >> >>>> context using custom properties with Aries JPA, something like: >> >>>> >> >>>> <bean id="contextWithProps"> >> >>>> <jpa:context property="em" unitname="myUnit"> >> >>>> <map> >> >>>> <entry key="openjpa.Log" value="slf4j"/> >> >>>> <entry key="openjpa.jdbc.DBDictionary" value="hsql"/> >> >>>> </map> >> >>>> </jpa:context></bean> >> >>>> >> >>>> That would be really useful as the behavior of the JPA layer would >> >>>> then >> >>>> be >> >>>> configurable via OSGi's ConfigAdmin. >> >>>> >> >>>> Luca >> >>>> >> >>> >> >>> >> >
