Re: WOLips resolving methods in the class hierarchy
Re: WOLips resolving methods in the class hierarchy
- Subject: Re: WOLips resolving methods in the class hierarchy
- From: Chuck Hill <email@hidden>
- Date: Tue, 5 Jun 2007 09:52:12 -0700
On Jun 5, 2007, at 3:04 AM, Edgar Ra. Klein wrote:
On 05.06.2007, at 11:13, Edgar Ra. Klein wrote:
On 05.06.2007, at 09:36, Daniele Corti wrote:
2007/6/5, Edgar Ra. Klein <email@hidden>: Hi,
I'm wondering whether I'm doing s.th. wrong or WOLips just cannot
resolve some methods in the model files.
I have generated _Class and Class-files using eogenerator. Now I
have
an instance of e.g. Author object, let say author, using in my
component and refer to it in the .wod file like author.firstName to
bind it to a WOString. Since the class Author extends _Author it
does
not have the method firstName, but _Author does.
My question: Is WOLips currently not resolving methods going up the
class hierarchy as expected?
well, this can have many causes. Try do these solutions:
1- Select "Project"-> Clean , and Clean and rebuilt you app (this
is a tipical problem of Eclipse: if you do changes on your
resources with other apps it doesn't see those changes, so it use
the old versions)
Use Refresh from the context menu or select the project in Package
Explorer and hit F5 to refresh. Having to do a Clean is a pretty
rare occurrence in my experience.
I already tried it, but it didn't work.
2- If WOLips doesn't still see the bind, you should try to see if
Your model is valid with EntityModeler (just click two times on
EoModel file to open it), and check if changes have been
committed at the model.
The model is up-to-date, still no change.
Is the model in the same project? If not, how are you including the
second project?
3- This happen to me a couple of times, everything seems ok, but
the app doesn't work, so, don't think bad of me, simply cancel
you .woo package, and rewrite it. Anfter this it works at me!
Don't ask me why, even though I didn't change anything, the
problem solved itself ;) However, now I have the problem that my
own components do not resolve :/ Even though the code completion
in the .wod-files does, hmmmmm...
This sounds like a reference problem. Are you referencing a built
version of something that is going away / changing? This is not
typical Eclipse behavior. You have done something strange.
Things become stranger and stranger... After a restart of Eclipse,
the initial problem came back and the component problem
disappeared, hmmmm...
Auto building replacing a referenced build product would explain that.
These two problems seem to occur alternately; but never both
together. Very strange behaviour...
So far for alternate occurrence... I really don't have a clue what
to do. My only suggestion is to ignore those two problems and go on
w/ coding ;) even though it makes being productive a bit more
complicated since I have to be aware of which errors to ignore or
to go after...
You need to go back and check the project structure and how things
are referenced.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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