cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emanuele Maiarelli <>
Subject Re: Different DataContext
Date Wed, 22 Jul 2009 14:13:35 GMT
and i will look into localObjects solution, this might lead to less concurrency problems...

Da: Emanuele Maiarelli <>
Inviato: Mercoledì 22 luglio 2009, 15:56:59
Oggetto: Re: Different DataContext

You welcome Reinout,

    I'm not familiar with Apache Wicket, and honeslty i'd like frameworks will handle all
ThreadLocal/contexts issues... 
and in the case of Wicket im not sure if there's a better way than the one i suggested

Da: Reinout van Schouwen <>
Inviato: Mercoledì 22 luglio 2009, 15:47:01
Oggetto: Re: Different DataContext


2009/7/22 Mike Kienenberger <>:
> If you know that Person is not in a modified state, you can make a
> local copy of Person in your nameObj's data context.

Thanks, Mike and Emanuele, getting the object context from the nameObj
indeed solves the problem.

Is this something to be aware of at all times? I.e. when creating a
link between two objects, is it best practice to retrieve the
datacontext from either one, and handle both objects from that

Reinout van Schouwen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message