RE: WO and Java 'packages'?
RE: WO and Java 'packages'?
- Subject: RE: WO and Java 'packages'?
- From: "Albert Jagnow" <email@hidden>
- Date: Wed, 21 Apr 2004 17:11:30 -0500
- Priority: normal
- Thread-topic: WO and Java 'packages'?
If you put everything in the same package everything will still be
together so it won't really make any difference. Things will work the
same as if everything was still in the java default package. As far as
I have experienced you only really need to pay attention when you have
things that are in differnet packages, like a framework that is
your.package.framework and an application that is
your.package.application. You just have to import
your.package.framework.* where you are using the code in your
application. I have had a few cases where I needed to specify the full
class path to make things happy, but it has not been a major pain.
Also I have several applications running in WO 5.2.3 with Java 1.4.2 not
using any package declerations and they seem to work fine.
--Albert
-----Original Message-----
From: Jonathan Rochkind [mailto:email@hidden]
Sent: Wednesday, April 21, 2004 4:43 PM
To: Chris Pavicich
Cc: email@hidden
Subject: Re: WO and Java 'packages'?
Shoot, that's a pain. I use lots and lots of frameworks, I have lots
and lots of code. Why don't you need to fully qualify for a component
in the same app, but you do for one in frameworks? I'm not used to
having to keep track of which components are in the app and which are
in frameworks; up to now it's never mattered, so long as the
component was accessible somehow. [Not to mention that sometimes the
pageWithName call is _itself_ in a framework, calling a component in
that framework or other frameworks].
Wait... did you use a different package name for each framework? If
what you're really saying is "You don't have to if they are all in
the same _package_, but you do if they are in different
packages"--that makes more sense to me, and is easier to deal
with---Initially I can just put everythign everywhere, even accross
multiple frameworks, in the same package. But that's not quite what
you said, I'm just making that part up.
?
--Jonathan
At 5:36 PM -0400 4/21/04, Chris Pavicich wrote:
>Jonathan:
>
>If you are making pageWithName calls to load a page from your app, you
>should be cool. If you are using them to load pages from a Framework,
>you will need to use a fully qualified name.
>
>The same thing will apply for WOD files. If you are using a component
>defined in a framework, you need to use the fully qualified name.
>
>If you need more help, feel free to contact me off-list, we just went
through
>this same thing not too long ago.
>
>HTH
>--CMP
_______________________________________________
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.
This e-mail (including any attachments) is covered by the Electronic
Communications Privacy Act, 18 USC. 2510-2521. It is confidential and
may be legally privileged. If you are not the intended recipient, you
are hereby notified that any retention, dissemination, distribution, or
copying of this communication is strictly prohibited. Please reply to
the sender that you have received the message in error, and then delete
it. Thank you.
_______________________________________________
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.