Re: [JBoss-user] EAR scoping and MANIFEST.MF references

[Scott M S. <Sco...@jb...>]

Yes, the only way you can guarentee package private access is to
include the classes from the package in the same jar. See bug #602828.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message ----- 
From: "Michael Bartmann" <mic...@li...>
To: <jbo...@li...>
Sent: Saturday, August 31, 2002 5:30 AM
Subject: Re: [JBoss-user] EAR scoping and MANIFEST.MF references


> Scott M Stark wrote:
> > Its not an issue of visibility, its that two classes from the same package
> > can be loaded by different class loaders and package private access
> > fails. I have seen this and the easiest way to cause it is to split the package
> > classes across two jars. An ear should use a common class loader across
> > all manifest references for this reason, and to also allow for ordering of
> > loading. Another problem that we do not have a solution for is loading
> > patch jars ahead of the jars the patch applies to. If you have a third party jar
> > and a patch for the jar the replaces some of the classes, you want to load the
> > classes in the patch jar ahead of the jar being patched. We have no way
> > to specify this currently. If there was a single class loader for all manifest
> > references that honored the order of the jar URLs given in the manifest
> > we could do this.
> > 
> Ok, this is exactly the reason I suspected. So I think that my
> workaround of referencing everything directly from the application.xml
> might eventually lead to problems too? If every third-party-jar is
> only referenced once in the application.xml each one should only be
> visible through one loader which seems to be the key issue.
> Or are there plans to "reduce" the number of classloaders?
> 
> thanks,
> michael