• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Package stratagies (are there some?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Package stratagies (are there some?)


  • Subject: Re: Package stratagies (are there some?)
  • From: Robert Walker <email@hidden>
  • Date: Wed, 16 Mar 2005 21:54:04 -0500

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.

I had a weird issue once with duplicate class name compile errors. I thought it was due the Java file for the WOComponent sitting in the root directory, but it's possible it was caused by something else.


On Mar 16, 2005, at 3:14 PM, Art Isbell wrote:

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:
email@hidden


This email sent to email@hidden


--
Robert Walker
www.robertwalker1.com

"There are 10 kinds of people in the world. Those who think binary and those who don't."

_______________________________________________
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


References: 
 >Re: Package stratagies (are there some?) (From: Colin Clark <email@hidden>)
 >Re: Package stratagies (are there some?) (From: Robert Walker <email@hidden>)
 >Re: Package stratagies (are there some?) (From: Art Isbell <email@hidden>)

  • Prev by Date: [RESOLVED]: Why can't I get <addObjectToBothSidesOfRelationshipWithKey> right?
  • Next by Date: Re: XHTML WOForm?
  • Previous by thread: Re: Package stratagies (are there some?)
  • Next by thread: DB Setting null value one a not null column
  • Index(es):
    • Date
    • Thread