[Esapi-dev] New Class loading Logic

[Jim Manico]

I approve of this message. :)

Tracking here:

http://code.google.com/p/owasp-esapi-java/issues/detail?id=100
>
> **Resource Loading**
>
> As has been discussed on this list, we need a flexible configuration 
> service  in 2.1 to provider generic features for default and custom 
> providers.  In regards to loading configuration files, I think the 
> following are needed:
>
> 1) Deployers may wish to adjust the order that class loaders are used 
> in the look up.   This is because:
>
> a) App servers all use different class loader hierarchies ( Kevin said 
> Websphere uses 5 ) and some such as Weblogic all you to adjust the 
> class loader hierarchy in the war's container specific deployment 
> descriptor ( weblogic.xml).
>
> b) Different organizations may want to be able to overide system wide 
> defaults ( system classpath) for a specific war and this requires 
> looking in System class loader after the ThreadContext class loader.
>
> 2) We may wish to override the resource search order ( file vs class 
> loader).  I can think of a few use cases for this and perhaps building 
> this into the service ( i.e. strategy plugin) is a lot easier than 
> requiring users to subclass the service.
>


-- 
Jim Manico
OWASP Podcast Host/Producer
OWASP ESAPI Project Manager
http://www.manico.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/esapi-dev/attachments/20100128/8fc3e41a/attachment.html