Kinda corny interjection, but I really liked this exchange. The civil
interaction is one of the things I really enjoy about the Cayenne community.
--
Kevin
On Wed, Apr 8, 2009 at 2:13 PM, Joseph Schmidt
wrote:
>
> Hi,
>
> Thank you very much for the quick response.
>
> > The 3.0 API was relax
Lawrence,
I am still struggling to understand Andrus' setCacheStrategy()
approach in his previous email (he claims it is simple and I am all
for that :) ). I am attempting some black box testing to figure out
exactly where my data object is getting cached (and not updated
properly). In
So, in my knowledge-gaining journey with this topic, I ran across this
page: http://cayenne.apache.org/doc/refreshquery.html, which looks
like a list of items yet to be done or at least yet to be documented
(and boy, when I have things really understood, I want to volunteer
some documentati
Dynamite. Thanks as always, Andrus. I'm going to get started with your
recommendation right away.
Lawrence
On Apr 10, 2009, at 6:09 AM, Andrus Adamchik wrote:
As mentioned in the quoted docs, there are ways to receive immediate
notifications on the individual objects updates (if they are u
As mentioned in the quoted docs, there are ways to receive immediate
notifications on the individual objects updates (if they are updated
via Cayenne). This approach, while the most powerful on the surface,
is least practical, especially across the VM. It suffers from a number
of shortcomin
The proposed way is to use JGroups or JMS for synchronization:
http://cayenne.apache.org/doc/configuring-caching-behavior.html
2009/4/10 Lawrence Gerstley
> So, I have the same question here--multiple thick clients (desktop RCP
> applications), each with a DataContext tied to the same backend, a
So, I have the same question here--multiple thick clients (desktop RCP
applications), each with a DataContext tied to the same backend, and
potential database access (direct or otherwise) from other toolsets
out of my control. Is there a recommended strategy for refreshing each
applications
