Hi all,
In Aries-CDI we have the issue that package scope methods are not working
because we used the classloader defining strategy - in OSGi we don't have
much choices with the extender pattern.
I'd like to go one step further and ensure it works - since it seems
working for weld.
I started a
Sorry for the late response, but I don't think you have to worry about
the hierarchical class loader scenario you described below.
At least in the server I'm aware of, the modules classloaders all
delegate up to the shared classloader. If they didn't then each
module classloader would be loading
, warA2, etc
- EAR-B -warB1, warB2, etc
But any proxies for e.g. javax.faces.context.FacesContext should not be loaded
with the EE-server-internal ClassLoader but maximum with EAR-A or EAR-B
ClassLoaders.
This means we should introduce an upper boundary ClassLoader detection somehow.
We
: Harald Wellmann hwellmann...@googlemail.com
To: u...@openwebbeans.apache.org; Mark Struberg strub...@yahoo.de
Cc:
Sent: Monday, June 25, 2012 4:47 PM
Subject: Re: Classloaders
Hi Mark,
hmm yes, I had thought the SingletonService might help, but I'm not
sure what it does and how to use
