"adrian(a)jboss.org" wrote : The second part of your comment doesn't make
sense.
| I think you are confusing explicit exports (named packages)
| with the "exportAll" behaviour (packages are discovered from a scan of the
deployment
| classpath).
|
| It is clearly trying to load to resource from the classloader and not finding
Both sars contain the same packages. Only the scoped one contains the blah.txt.
This is trying to load it from the correct child domain.
| 2007-10-12 11:33:46,015 TRACE [org.jboss.classloader.spi.base.BaseClassLoaderDomain]
ClassLoaderDoma
| in@11b3435{aop.loading:loader=scopedextender1} trying to get resource
org/jboss/test/aop/scopedexten
| der/blah.txt from all exports null
|
The rest of the logging seems to be trying to load from a parent (which does not have the
resource)
| 2007-10-12 11:34:10,906 TRACE [org.jboss.classloader.spi.ClassLoaderDomain]
ClassLoaderDomain@11b343
| 5{aop.loading:loader=scopedextender1} org/jboss/test/aop/scopedextender/blah.txt
matches parent afte
| rFilter=<EVERYTHING>
| 2007-10-12 11:34:10,921 TRACE [org.jboss.classloader.spi.ClassLoaderDomain]
ClassLoaderDomain@11b343
| 5{aop.loading:loader=scopedextender1} get resource from parent
org/jboss/test/aop/scopedextender/bla
| h.txt parent=ClassLoaderDomain@1f21056{<DEFAULT>}
|
For the domain, when registering classloaders the packages are added correctly. For the
scoped domain, they are not
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094562#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...