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

"Jerry W. Walker" <[email protected]>
Newsgroups gmane.comp.web.webobjects.devel
Message-ID <[email protected]>
Hi, Servidor,

On Mar 2, 2006, at 11:44 AM, servidor forja wrote:

> Sorry for my English (Im from Mexico), the problem IS when  
> modifying the component and saving with WebObjects builder
> (not using it to modify and save a record).

Your English was fine, native English speakers (myself included)  
often similarly leave information out.

> -I re-ran repair permissions
> -Re-installed xcode with all its options
> -Checked permissions on the folder of the project (Users/admin/ 
> _Dev2006/_FraccDB7/)
>  it has (owner=admin, RW)(group=staff, RW)(other, RW) on every  
> folder on the path, and including the xx.wo package)
> and the error keeps showing, the .wo file disappears.
> -Sometimes when I save a component when in the source mode the  
> error wont happen but ar returning
>  to layout mode all bindings in the layout mode appear as unknown.
> -Also, I was used to switch to source mode to manually modify html  
> and the window was split with bindings at the bottom,
> now it seems to show only the html (OR I DONT KNOW HOW TO SHOW IT)

The directories in the project path also need Execute permissions.  
That is, each directory, from your project directory down through the  
directory for the component package needs Unix permissions rwx------  
at least for the admin user when you're logged in as admin. Read and  
write permissions are not sufficient, but this may not be so easily  
seen through the Finder.

Start a Term.app window, navigate to the directory and check the  
permissions of the component's package directory and the parent  
directory containing that package.  You can use the Unix command "ls - 
lsd <name>" where <name> is the name of the directory you're trying  
to list to see these permissions directly.

If both directories have execute permissions as well, and what you're  
saying is correct, I honestly have no idea what's causing your problem.

There are things we know, however, and things I think we can safely  
infer from what you've said:

We know:

   * WOBuilder attempts to rewrite the WOComponent package each time  
you make a change. (i.e. WOBuilder rewrites the xx.html, xx.wod,  
xx.woo files along with the xx.wo directory containing them and other  
files and directories contained therein, e.g. CVS directories) and  
remove the old package when successful.

   * WOBuilder's failure to write that package leads to the message  
you're seeing.

We can infer:

   * something is stopping WOBuilder from rewriting the package when  
a change is made.

   * failure to rewrite the package is probably causing the other  
problems you're having with WOBuilder

At best, I can only say, good luck, at this point. Perhaps others  
could shed more light on this.

Regards,
Jerry

> thank you
>
> On Mar 1, 2006, at 12:14 PM, Jerry W. Walker wrote:
>
>> 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
>


--
__ 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.