On 21/03/2013 08:09, Violeta Georgieva wrote:
> 2013/3/20 Mark Thomas wrote:
>> On 20/03/2013 13:55, Violeta Georgieva wrote:
>>> Hi,
>>>
>>> I have a question for the loader that is used in
>>> o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
>>> JarScannerCallback, Set) (7.0.x
2013/3/20 Mark Thomas wrote:
> On 20/03/2013 13:55, Violeta Georgieva wrote:
>> Hi,
>>
>> I have a question for the loader that is used in
>> o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
>> JarScannerCallback, Set) (7.0.x trunk).
>>
>> Why don't we use the loader that is pro
On 20/03/2013 13:55, Violeta Georgieva wrote:
> Hi,
>
> I have a question for the loader that is used in
> o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
> JarScannerCallback, Set) (7.0.x trunk).
>
> Why don't we use the loader that is provided as a method parameter,
> but i
Hi,
I have a question for the loader that is used in
o.a.t.util.scan.StandardJarScanner.scan(ServletContext, ClassLoader,
JarScannerCallback, Set) (7.0.x trunk).
Why don't we use the loader that is provided as a method parameter,
but instead of this we are using the thread context class loader?