Hi, Corin,
I would suggest using FileMerge to compare the new and old versions
of bottledomains.eomodeld. Every time I've gotten this message on a
system that has been running successfully in the past, it was because
of file corruption. I've found it helpful in each case to figure out
what caused the corruption with FileMerge.
The results have usually been instructive and helped me avoid actions
that would cause such corruption to occur in the future. Note that
this has not always been the case. A couple times the source of the
corruption was just not obvious beyond a guess at a broken EOModeler.
Regards,
Jerry
On Dec 28, 2005, at 9:14 PM, Corin Lawson wrote:
Thanks,
It seems that option 3 was likely as reverting to an old code model
fixed the problem...
On 29/12/2005, at 1:03 PM, Chuck Hill wrote:
1. That file is, in fact, missing
2. The user the app is running under lacks permissions to read the
directory / files in the directory
3. One or more files in the model directory is corrupt.
Chuck
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
[EMAIL PROTECTED]
203 278-4085 office
_______________________________________________
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]
