Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41728784.2030203@gluecode.com>
Date: Sun, 17 Oct 2004 07:53:56 -0700
From: Jeremy Boynes <jboynes@gluecode.com>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: JSTL Broken
References: <Pine.LNX.4.58.0410162120280.27069@saturn.opentools.org>
In-Reply-To: <Pine.LNX.4.58.0410162120280.27069@saturn.opentools.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Aaron Mulder wrote:
> 	So our JettyClassLoader denies any requests starting with "javax".  
> Unfortunately, this appears to break the JSTL, which includes a JAR with
> javax.servlet.jsp.jstl.* packages.  That breaks Spring, which is blowing
> up trying to load the LocalizationContext class from the JSTL when you use
> a JSTL view for Spring.
> 
> 	I guess we need to include the JSTL classes as part of Geronimo?  
> In the mean time, I'm going to disable the "javax" restriction, so I can 
> continue to package it in my WAR.
> 

SRV.9.7.2 basically says we should not allow applications to override 
things in the java.* and javax.* namespaces. On other hand, JSTL is not 
an API required by the spec.

I think that we are being too conservative here. Better logic might be 
to search for java and container classes in the parent classloader first 
and the war second, and all other classes in the war first and the 
parent second.

This would prevent the war overriding container classes but would still 
it to use versions it supplied if the container did not have them.

---
Jeremy