> I remember last time around we were talking about being able to wrap
> the ServletContext instance so that the getResource methods could be
> overridden. Perhaps this is a simpler alternative to that.
Interesting. My initial reaction was that a wrapper approach might be
simpler because it would be less specific. But then the scope of the
change might also be too broad: We would have to consider consequences
of overriding each of the ServletContext methods, many of which would
probably break the spec and/or break other code/behavior if changed.
So perhaps the ResourceLoader design is simpler, at least the scope of
the change would be smaller and its implications more forseeable.
cheers,
Eirik.