Re: Package stratagies (are there some?)
Re: Package stratagies (are there some?)
- Subject: Re: Package stratagies (are there some?)
- From: Art Isbell <email@hidden>
- Date: Wed, 16 Mar 2005 10:14:09 -1000
On Mar 16, 2005, at 9:58 AM, Robert Walker wrote:
1. Do folks even use packages ? or do most people put everything in
the default package?
Yes it is a good idea to use package for all classes.
Agreed.
If you put all classes in packages you will need to change the default
file structure after creating your project.
Hmm, maybe I've been lucky, but I have never changed the default Xcode
project file structure, either for frameworks in packages or for apps
in packages.
You may get errors if you leave your WOComponent java files in the
root of the project directory.
I never have.
Also you will need to move your EOModel files into the BusinessLogic
subfolder where your business objects live. This is due to a goofy
bug the current version of EOModeler. If the class files are not in
the same directory as the model file you never get the "Merge" option
when generating your EO classes. I really hope Apple fixes this in
the next release.
I guess I've never experienced this bug because my class files and
eomodels are all in the root project directory.
I like to just throw everything in a single package representing my
application.
I do the same. Each framework is in its own package as well.
If I recall, I made only the two changes that Colin described when
moving from the default package to custom packages:
- I changed the class names in eomodels to fully-qualified class names,
- I defined WOAPPLICATION_CLASS_NAME in Xcode's project's target to the
fully-qualified Application class name.
Aloha,
Art
_______________________________________________
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