Hi Arnaud,
I haven't worked with Wicket, but...
1. If MyFacade is a singleton, createDataContext() is the correct way to
create a context. getThreadDataContext is used when a context is bound to
every thread, e.g. if you want to have a separate context for every user's
session. This is likely your case. To bind a context to every session, use
something like WebApplicationContextFilter (works only if you have one
domain, you need something more complicated otherwise)
2. If you bind context to a session, as described in #1, you won't have SQL
request at every refresh.
2009/9/7 Arnaud Garcia <arnau..magemed-87.com>
> Hi list,
>
> I am using cayenne and wicket, and I found no example to integrate
> both framework....
>
> well, just a question of design for using the datacontext...
>
> Is it ok to use the datacontext in a singleton like this for a webapp
>
> private MyFacade() {
> ctxt = DataContext.createDataContext("DOMAIN1");
> }
> => I ask this question since I saw on the documentation for webapp to
> use a getThreadDataContext ??
>
> 2/ About cache strategy...
>
> I have a big request on oracle, so I decided to use the
> QueryCacheStrategy.LOCAL_CACHE, but each time I refresh the webpage
> the request it always done...
>
> Is it because I didn't use correctly my datacontext ? do I have to
> create a new one each time using createDataContext ?
>
>
> thanks for help
>
>
> arnaud
>
-- Andrey
This archive was generated by hypermail 2.0.0 : Mon Sep 07 2009 - 11:41:26 EDT