Is there any other reason that you need a custom BrokerFactory than this
bit of functionality?
On Tue, Nov 11, 2014 at 8:53 AM, Jörn Gersdorf
wrote:
> Hi all,
>
> I´ve reported the OSGi ClassLoader issue as
> https://issues.apache.org/jira/browse/OPENJPA-2542.
>
> Kind regards,
> Jörn
>
> On Tue
Hi all,
I´ve reported the OSGi ClassLoader issue as
https://issues.apache.org/jira/browse/OPENJPA-2542.
Kind regards,
Jörn
On Tue, Nov 11, 2014 at 3:33 PM, Jörn Gersdorf
wrote:
> Hi Rick,
>
> thanks for you thought. The reason I´m using the custom JDBCBrokerFactory
> is that I want to have the
Hi Rick,
thanks for you thought. The reason I´m using the custom JDBCBrokerFactory
is that I want to have the QueryCache disabled _by default_ and only enable
it on occasion. With the out-of-the-box-JDBCBrokerFactory it´s only
possible the other way around (disable on occasion).
Now, my custom JD
Hi Rick,
thanks for you thought. The reason I´m using the custom JDBCBrokerFactory
is that I want to have the QueryCache disabled _by default_ and only enable
it on occasion. With the out-of-the-box-JDBCBrokerFactory it´s only
possible the other way around (disable on occasion).
Now, my custom JD