Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 41121 invoked by uid 500); 28 Jan 2003 16:04:18 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 41108 invoked from network); 28 Jan 2003 16:04:18 -0000 X-Sent: 28 Jan 2003 16:03:53 GMT Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 To: cocoon-users@xml.apache.org From: "Cameron McKenzie" Subject: Re: WebSphere 5.0 and cocoon X-Sent-From: mail@cameronmckenzie.com Date: Tue, 28 Jan 2003 08:03:52 -0800 (PST) X-Mailer: Web Mail 5.2.0-3_sol28 Message-Id: <20030128080353.6036.h001.c015.wm@mail.cameronmckenzie.com.criticalpath.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Really think I've licked the WebSphere 5.0 problem now. The trick is this. Make sure the application server classloader is set to MODULE visibility. Then set the classloader on the ear to PARENT_LAST and then again, set the classloader on the war module to PARENT_LAST. Once you've made these changes, the cocoon war should run without a hitch. Good luck. -Cameron McKenzie --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: