Re: Just upgraded to tiger server with X code 2.2.1 and WebObjects builder has problems

Hi, Servidor,

On Feb 28, 2006, at 7:49 PM, servidor forja wrote:

> Sorry for the reposting, but the first post got to the wrong tread
>
>
> I have a project that works well on panther server but I needed to
> upgrade to tiger server for several reasons.
>
> My problem is that after I cleanly installed tiger, X code, updated
> everything, and opened my project, which gets upgraded and compiles
> without errors
> and works fine. i get
> ---------
> Unable to create backup file for /Users/admin/_Dev2006/_FraccDB7/
> FrentesListEditPage.wo: Error removing
> --------------
> When i open a component change anything and SAVE, also i lose the
> xx.wo (becomes unreadable)
> HD passes Disk Utils, permissions are OK, and i run as an admin
> this is the developer server.

It's been a long time since I've seen this error, but IIRC, it tended  
to be caused either by a permissions problem (which you said you've  
already checked) or by another tool (e.g. Term.app) working within  
the component's package directory.

I don't remember this problem ever occurring while the application  
was running, but rather when changing a WOComponent in WOBuilder and  
trying to save the changed page.

I'm running on Tiger, not Tiger Server, but I've just tried to  
recreate the error and it seems that navigating Terminal to the  
WOComponent directory no longer causes the problem. After re-saving  
the component, Term was confused about it's current working directory  
but that doesn't seem to trigger the error. On the other hand, when I  
changed the permissions on the component's parent directory to  
disallow writing within the directory, I was able to reproduce the  
message you got.

Be sure that you're not only checking the permissions of the  
WOComponent package directory and each of the files contained  
therein, but also the permissions set for the component's parent  
directory.

> I have another question is it safe to keep using EOModeler, because i
> dont like the new interface?

Yes, the old EOModeler still works fine. The new EOModeling tools in  
Xcode are not yet ready for prime time. In short, avoid using them at  
this stage.

Regards,
Jerry

--
__ Jerry W. Walker,
    WebObjects Developer/Instructor for High Performance Industrial  
Strength Internet Enabled Systems

     [email protected]
     203 278-4085        office

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev