Re: WOBuilder bug?
Re: WOBuilder bug?
- Subject: Re: WOBuilder bug?
- From: John Larson <email@hidden>
- Date: Wed, 11 Jul 2007 11:58:25 -0500
Thanks Simon,
I tried cleaning eveything and restarting Eclipse to no avail. I
looked at my build path and everything looked fine, and the app ran
and debugged fine so I assume it was "really" okay. The error was
coming from the builder module, so I assumed it was a builder problem.
I thought that the builder architect may have been searching the
eclipse build path for a wo component of some name and then using the
class file associated with that name - even if that class is in a
different project. This was further validated by the fact that the
auto complete found the component name but cannot then offer any
bindings. Further, the component in the first project
(alphabetically) works fine in builder but not in subsequent
projects. As soon as the first project is removed, then the new first
project works fine though it was previously in error.
John Larson
President
Precision Instruments, Inc.
Ph: (847)824-4194
Fax: (866)240-7104
Sent from my iPhone
On Jul 11, 2007, at 11:39 AM, Simon McLean <email@hidden> wrote:
These kind of errors are normally build-path related.
Try cleaning all your projects and an Eclipse reboot won't hurt (I
believe Eclipse only loads the classpath at boot and doesn't pick up
any changes to it thereafter).
As a last resort I would edit your build path and just shuffle the
order of items in there which will force various files under your
projects woproject dir to be rewritten.
If all of the above fail then typically I swear a little (or
sometimes a lot), then bin my project and check-out from source
control again. This is absolutely last resort though, and serves as
a reminder to make regular commits... :-)
Simon
On 11 Jul 2007, at 17:29, John Larson wrote:
Mike,
I wanted to remember that you were the contact on WOBuilder for
Eclipse. If I'm wrong, let me know and I'll pass this along to the
right person. First, I can't thank you all for all the work you do
with Wonder and Eclipse. I wish I had enough talent to contribute
too.
In my workplace I had two completely different projects that both
had WO components with the same name. When I tried to use the Foo
component in the second project's components I would get an error
that the class Foo is either missing or does not extend
WOComponent. This went away when I moved the first project out of
the workspace. So I don't know if you want to look at how you are
getting your handle to the wo component class in the builder or if
you have any other comments.
John
_______________________________________________
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