Re: WebObjects Builder ... again
Re: WebObjects Builder ... again
- Subject: Re: WebObjects Builder ... again
- From: Francis Labrie <email@hidden>
- Date: Fri, 9 Jul 2004 21:13:02 -0400
Hi Ben,
Ben Ketteridge wrote:
> Has anyone else experienced this...
>
> Our project is now rather large (about 10 people have been working on
> this for about 5 years), and WOBuilder is struggling to manage our
> WOComponents. We can no longer see the session and application objects
> in the bottom left panel, and this is just the simplest problem with
> it. Other class properties are starting to go missing.
Well, I suspect you are using single class imports in your class
component, i.e.:
import com.webobjects.appserver.WOComponent;
Instead of the package import:
import com.webobjects.appserver.*;
Don't you? This is an old and very annoying bug in WOBuilder. You must
at least import these packages to keep WOBuilder happy:
Component classes:
import com.webobjects.appserver.*;
import com.webobjects.foundation.*;
Direct action classes:
import com.webobjects.appserver.*;
> This appears to be a progressive degredation in performance as our
> projects get larger. Has anyone any suggestions?
>
> We're working on Windows (no, don't suggest MacOSX, it is simply not
> an option for political reasons), and the project has 540 EO entities
> and 794 .wo folders across 20 interrelated projects. (626,000 lines of
> Java!)
If the Java classes imports are the problem, the best solution would be
to perform a batch script to detect all component and direct action
classes and add to them all the needed package imports. You don't need
to remove each individual class import: the Java compiler won't
complain.
--
Francis Labrie
Saint-Bruno-de-Montarville, Quebec, Canada
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.