That's correct Mike. Also, thus far, I could only get OpenJPA slice working with DBCP. There seems to be an issue with using Tomcat Connection Pool. Once I have more time to trace/debug what's going on, I'll post it on a new thread.
Richard. On Wed, Aug 3, 2011 at 11:01 AM, Michael Dick <michael.d.d...@gmail.com>wrote: > I think Richard's configuration is correct. The only catch, which he > pointed > out, is that you do have to specify the DBDictionary to use. Maybe I > missed > something though? > > I'm not sure whether having to specify the DBDictionary is the result of > the > automagic connection pool support, but for the time being we should update > the documentation to reflect this requirement. > > In case I missed something, here's the persistence unit from the > openjpa-slice module that I used to reproduce the problem : > http://pastebin.com/W47zy9ms > > -mike > > On Wed, Aug 3, 2011 at 10:05 AM, Pinaki Poddar <ppod...@apache.org> wrote: > > > The connection pooling can be configured for each slice as you would do > > normally [1] for a single database. The property names however will > change. > > > > <property name="openjpa.slice.One.ConnectionProperties" value=..../> > > > > However, we have introduced some new mechanics that can configure a > > connection pool automagically when commons dbcp in classpath. I do not > > think > > that this new mechanics have taken Slice connection establishment into > > account. > > > > > > [1] > > > > > http://openjpa.apache.org/faq.html#FAQ-HowdoIenableconnectionpoolinginOpenJPA%253F > > > > ----- > > Pinaki Poddar > > Chair, Apache OpenJPA Project > > -- > > View this message in context: > > > http://openjpa.208410.n2.nabble.com/Slice-and-connection-pools-tp6643295p6649074.html > > Sent from the OpenJPA Users mailing list archive at Nabble.com. > > >
