Re: Package stratagies (are there some?)
Re: Package stratagies (are there some?)
- Subject: Re: Package stratagies (are there some?)
- From: Colin Clark <email@hidden>
- Date: Wed, 16 Mar 2005 14:13:47 -0500
1. Do folks even use packages ? or do most people put everything in
the default package?
Yes, I expect that most people definitely use packages. There's no
reason not to, and they're a great way to clearly partition your code.
2. There is no importing a class from the default package since in JDK
1.4 , so references to this practice in the mail archives must be from
an earlier time, right? (It doesn't work for me.)
You shouldn't have to import anything that is in the default package.
It's automatically available.
3. What EO/WO references need to specify the qualified-with-package
class name besides the EOModeler Class specification?
As you say, the class name for your entities should be the fully
qualified version (eg. my.package.Class). You do need specify the
fully-qualified name of your WOApplication subclass by defining the
WOAPPLICATION_CLASS_NAME variable in your project's target in XCode.
4. Any other "gotchas" in reference to this?
Nope, it's pretty straightforward. I've never had any problems related
to packages. Keep in mind that if you don't define package membership
for all your classes, you'll likely run into difficulties if you
eventually choose to deploy your application as a servlet.
Colin
---
Colin Clark
Dynamic Web and Database Development Lead,
Resource Centre for Academic Technology,
University of Toronto
_______________________________________________
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