Joe Emenaker wrote:


>> It's also possible that 2 different (but very close) APIs have classes in
>> the same package.
>  
> What is Java supposed to do if it encounters two different classes of the
> same name in the same package? Does it just take the first one that it
> encounters?

While having classes for a package spread over multiple jars is possible, I
think the policy should discourage it.  If a signed jar is added to the mix,
then it is a security exception to try to load classes from the same package
from different jars.

cheers


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to