I guess, you use default (package-protected) if something is an internal
implementation detail shared within a particular package; but it needs
to be shared, otherwise, why expose it, even inside a package?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
>
"Default" means "package protected" - other classes in the same package can
call those methods/fields, kind of the same as "protected".
The slight difference from "protected" is that inheriting classes in other
packages cannot access the "package protected" methods/fields, only the
"protected" and
| package; but it needs to be shared, otherwise, why expose it,
| even inside a package?
i know what it means. i ask the opposite question: why would i hide it
?
regards, tom.
| > -Original Message-
| > From: [EMAIL PROTECTED]
| > [mailto:[EMAIL PROTECTED] On Behalf Of
| > Tom Baeyen
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Tom Baeyens
> Sent: Wednesday, January 04, 2006 8:15 AM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] basic java design question
>
> | package; but it needs to be shared, otherwise, why
Because then we have integration issues like relying on non-public API
of deployers, jms impl, etc. "I can use everything I can see".
Tom Baeyens wrote:
| package; but it needs to be shared, otherwise, why expose it,
| even inside a package?
i know what it means. i ask the opposite question:
m Baeyens
> Sent: Wednesday, January 04, 2006 10:15 AM
> To: jboss-development@lists.sourceforge.net
> Subject: RE: [JBoss-dev] basic java design question
>
> | package; but it needs to be shared, otherwise, why expose it,
> | even inside a package?
>
> i know what it me
