Re: Bizarre Behavior
Re: Bizarre Behavior
- Subject: Re: Bizarre Behavior
- From: Florijan Stamenkovic <email@hidden>
- Date: Fri, 11 Feb 2005 14:14:07 +0100
1. Sorry, can't see where the problem is in this one. However,
EOModeler is by itself an extremely buggy program. Irritatingly so
even. I am almost expecting it to crash every now and then, or just not
to show a certain attribute or whatever... Hope they address this...
2. I think the problem is in you inserting your model and creating
groups in the insertion process. Made the same mistake once. If I am
understanding your problem right, this is the way to deal with it: say
"Insert existing files" somewhere in your project, find your model, and
when Xcode displays the next window, choose "Copy files..." switch box,
choose to insert the file into the Application Server target, and
choose to create folder references and NOT groups. Xcode will probably
represent your model with a blue folder icon, but when you double click
it he will open it in EOModeler, and will not report any mistakes in
building.
In Xcode a yellow folder represents a group, and a blue one represents
a folder reference. Since eomodeld files are bundles by nature (folders
represented as files in the file system), Xcode will see them as
folders, and unless you choose "create folder references" when
inserting a model, he will interpret the eomodeld folder as a group and
therefore will not be able to treat him properly.
Hope this helps
Cheers
Florijan
On Feb 11, 2005, at 09:22, Jay Martin wrote:
All,
I'm hoping someone can help. I'm having 2 issues with WO:
1) EOModeler is behaving strangely: after having it snarf an existing
mysql db to get tables, etc, when I switch to model view to connect my
relationships, none of the fields in any of the tables is
independently highlightable. It's as if the whole box representing the
table is just one large static image. I can move it around as a whole,
but not select a specific line. Interestingly enough, it doesn't seem
to happen if I create the model from scratch.
2) No matter how I attempt to add an EOModel file into my project in
Xcode, it gets inserted as a yellow folder. This, of course, means
that Xcode thinks it's just another folder. I can't double-click on it
to open EOmodeler. That in itself isn't that big a deal (just really
inconvenient), but since Xcode doesn't seem to know that it's special,
it doesn't get built right. When I run my app it can't find the model.
My environment:
Mac OS X Server 10.3.8 (although same behavior on 10.3.7)
Java 1.4.2_05-141.3
WebObjects 5.2.3 (although same behavior on 5.2.2)
I've completely uninstalled WO and reinstalled (well, as completely as
the uninstaller and manual removal of apps allows). Twice. Nada.
On a side note, it seems that I've always had some strange issue or
other with the WO dev environment in general (I've been using it
sporadically since 4.5). Is it me or is it pretty fragile? Deployed
apps are solid, but the tools seem to break in some way or another
everytime I sneeze. I'm so paranoid about OS upgrades that I find
myself using other tools, which is a real shame since WO (when it
works) is so wonderful.
BTW, I also installed WO 5.2.3 on an iMac G5 (10.3.7 client) and had
some symptoms of #2, but after I saved my model in EOModeler the first
time AFTER inserting it into the project the icon in Xcode changed to
the normal .eomodel icon and it's happy. No issue #1.
Ideas!?
jay
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden