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 67114 invoked from network); 3 Feb 2000 03:17:08 -0000 Received: from phoenix.webslingerz.com (balld@206.66.49.24) by 63.211.145.10 with SMTP; 3 Feb 2000 03:17:08 -0000 Received: from localhost (balld@localhost) by phoenix.webslingerZ.com (8.8.7/8.8.7) with ESMTP id WAA24390 for ; Wed, 2 Feb 2000 22:12:48 -0500 Date: Wed, 2 Feb 2000 22:12:48 -0500 (EST) From: Donald Ball To: cocoon-dev@xml.apache.org Subject: Re: RunTimeException in XSPProcessor In-Reply-To: <004001bf6dc7$e7615b60$724695c1@acidbox> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 2 Feb 2000, Jeff Martin wrote: > I'm getting a RunTimeException everytime I try to access an XML page > under Linux but not NT. Can anyone shed and light on this. > > I've been developing some pages using Cocoon 1.6.1 under NT JDK1.2.2. > I've just started to create a new enviroment on Linux using Blackdown > JDK1.2.2 (I've tried the sun release to) when I try and use any of the > example xml pages I get and RunTimeException Error loading logicsheet: > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl > from org.apache.cocoon.processor.xsp.XSPProcessor. > > I've had a poke around the code and this is the bit that causing me > problems. When the url is created using > resource://org/apache/cocoon/processor/xsp/library/java/cookie.xsl > this is throwing an exception because it doesn't know how to handle > the url. I wasn't aware the there was a resource protocol handler but > as this code works fine on NT there must be. I have managed to put a > hack in which uses this.getClass().getResourceAsStream(location) after > choping the resource: of the front of location. > > Anyone got any comments. This may have to do with a serious flaw in the way the JVM works with URLFactories. I don't understand all of the details, but the gist is that only one URLFactory may exist in a JVM, whih essentially means that only one application may add support for additional URLs to the JVM. Is it possible that, on your linux server, another servlet has already created a URLFactory? As I understand it, Stefano, et. al. are _actively_ looking for an alternate solution. Do you have any suggestions? - donald