Hi Corin,
this might seem remedial, but the way I tested it when running
multiple instances of an application was to fetch in the data on one
instance, change the relationship on another, and then refetch it to
see if the relationship was updated. In your case, you would need to
change it on the non-WO app.
You may also want to look into some change notification frameworks
such as Wonder's ERChangeNotificationJMS. Quite a lot has been
written on the topic of fresh data, take a look at this:
http://wiki.objectstyle.org/confluence/display/WO/EOF-Using+EOF-
Caching+and+Freshness
Gordon
On 28-Sep-07, at 5:14 AM, Corin Lawson wrote:
Thanks Gordon,
I'll be sure to try it, but how do I test?
Cheers,
Corin.
On 27/09/2007, at 11:24 PM, Gordon Belray wrote:
Hi Corin,
this has worked for me in the past:
EOFetchSpecification fs = new EOFetchSpecification("SomeObject",
null, null);
fs.setRefreshesRefetchedObjects(true);
String [] keypaths = {"toRelationship"};
fs.setPreftechingRelationhsipKeyPaths(new NSArray(keypaths));
cheers,
Gordon
On 27-Sep-07, at 1:12 AM, Corin Lawson wrote:
Hi List,
I have been experiencing the following problem for some time now
and have not been able to establish a pattern or replicate the
problem, let alone solve it, please help.
The symptom is that a certain process fails because the WO
(5.2.4) app is using stale or cached data, where the data has
been changed in the database (mysql 5) by a separate (non-WO)
system. The stale data has been known to persist for over an
hour. The data in question is contained in an entity that is a to-
many relationship of another entity which is being fetched.
From inspecting the standard output with
DEOAdaptorDebugEnabled=true I see that in the majority of cases
the entity in question and all it's related entities are being
fetched each time that the process is executed. But in other
cases (which are indistinguishable from the other cases AFAIK)
only the entity is fetched and none of it's related entities. In
all my test cases it works as I expect it to work. It is
extremely frustrating that I cannot replicate the problem.
What debugging info can I turn on to distinguish the problem case
from ok case?
I have tried various approaches to fix the problem, even
regularly calling invalidateAllObjects() on the EOEditingContext
but to no avail.
Cheers,
Corin.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/
gordon.belray%40utoronto.ca
This email sent to [EMAIL PROTECTED]
Gordon Belray
Information Architect and Imaging System Manager
Information Technology Services Robarts Library
416.946.8617 cell: 416.427.7007
[EMAIL PROTECTED]
Gordon Belray
Information Architect and Imaging System Manager
Information Technology Services Robarts Library
416.946.8617 cell: 416.427.7007
[EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
