Re: Different DataContext

From: Emanuele Maiarelli (evvdra..ahoo.it)
Date: Wed Jul 22 2009 - 10:13:35 EDT

  • Next message: Mike Kienenberger: "Re: Different DataContext"

    and i will look into localObjects solution, this might lead to less concurrency problems... ________________________________ Da: Emanuele Maiarelli <evvdra..ahoo.it> A: user@cayenne.apache.org; reinout@gmail.com 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 <reinou..mail.com> A: user@cayenne.apache.org Inviato: Mercoledì 22 luglio 2009, 15:47:01 Oggetto: Re: Different DataContext Hi, 2009/7/22 Mike Kienenberger <mkienen..mail.com>: > 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 context? -- Reinout van Schouwen http://vanschouwen.info/

    This archive was generated by hypermail 2.0.0 : Wed Jul 22 2009 - 10:31:34 EDT