Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 25756 invoked from network); 20 Feb 2001 21:15:57 -0000 Received: from rs4s1.datacenter.cha.cantv.net (200.44.32.54) by h31.sny.collab.net with SMTP; 20 Feb 2001 21:15:57 -0000 Received: from promca.com ([200.11.151.1]) by rs4s1.datacenter.cha.cantv.net (8.10.2/8.10.2/2.0) with ESMTP id f1KLFwk19127 for ; Tue, 20 Feb 2001 17:15:58 -0400 Message-ID: <3A92DFD2.6080704@promca.com> Date: Tue, 20 Feb 2001 17:21:22 -0400 From: Robert Marcano User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; 0.8) Gecko/20010215 X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [C2] Regression in classpath generation -- Someone take a look at this please References: <3A925EDA.7000401@promca.com> <3A92722A.EB91EBF@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Berin Loritsch wrote: > Robert Marcano wrote: > >> > > > It was removed. Now, consider Servlet Engines like IBM WebSphere 3.5.2 > (Any previous version is not guaranteed to work), that not only have > broken classloaders, they physically rearrange the webapp. In those cases > (in order for compilation to work) you will have to recopy the jars into > the proper location again. > > With the Servlet 2.2 spec and Servlet 2.3 spec, one would think that rearranging > the war file is not only too much manipulation, but that those contracts should > be guaranteed even if you place the jars somewhere else... > > There is much I have grown to dislike about WebSphere. The reason why it is rearranged is for security reasons, in order to protect the java code from improper downloads. I think that is posible to get a workaround until the servlet spec defines a standard way to get the web application classpath