Re: [eclipselink-users] Accessing EclipseLink cache OR coordination wit

[Tim Hollosy <hollosyt@xxxxxxxxx>]

They hit the same caches L1 and L2, they're a great option we use them
quite a bit rather than raw jdbc.


./tch



On Tue, Feb 17, 2009 at 9:25 AM, Guillaume Bilodeau <gbilodeau@xxxxxxxxx> wrote:
>
> I've just read about JPA native queries and it looks like an interesting
> option instead of using plain JDBC statements.  Are native queries hitting
> the EclipseLink cache or does it require some form of manual integration?
>
> Cheers,
> GB
>
>
> Guillaume Bilodeau wrote:
>>
>> Hi guys,
>>
>> We're looking into using EclipseLink in a web application targeting
>> WebLogic 10.3 where data access would be done using both JPA and native
>> JDBC.  We will need aggressive caching to achieve short response times and
>> ideally, a cache shared between both mechanisms would be used.
>>
>> From what I gather, EclipseLink doesn't support external cache providers
>> such as EHCache but instead relies on an internal strategy to store, query
>> and invalidate cached data.  The native JDBC connections could leverage
>> that cache, but I can't find any API to interact with it.  Using two cache
>> managers is out of  the question since it would bring too many stale data
>> and coordination issues.
>>
>> Am I missing something or is sharing a cache between EclipseLink and
>> native JDBC impossible?
>>
>> Thanks all,
>> GB
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Accessing-EclipseLink-cache-OR-coordination-with-EHCache-tp22046013p22058357.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>