Hi Arnaud,
Op dinsdag 08-09-2009 om 09:31 uur [tijdzone +0200], schreef Arnaud
Garcia:
> many thanks .. I start with cayenne and wicket... so it is a bit hard to
> start..
Take a look at Databinder (www.databinder.net) - it provides a glue
layer between Wicket and Cayenne. It's not without its
Hi Arnaud,
Have a look at recent discussion:
http://cayenne.markmail.org/message/3zcm4dw2ttbfjqwq?q=list:org.apache.cayenne.user&page=6#query:list%3Aorg.apache.cayenne.user+page:6+mid:3zcm4dw2ttbfjqwq+state:results
2009/9/8 Arnaud Garcia
> Thank you Andrey,
>
> 1/ hmmm, so that means that when
Thank you Andrey,
1/ hmmm, so that means that when I use in a webapp a Datacontext like:
ctxt = DataContext.createDataContext()
The DataContext is destroy at the end of the request ? this is why I
do not my cache working
2/ To bind the DataContext to the user session I need to use the
filt
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 you
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("D
