cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject [Fwd: failure notice]
Date Sat, 30 Dec 2000 03:44:35 GMT


-------- Original Message --------
Subject: failure notice
Date: 29 Dec 2000 14:48:44 -0000
From: MAILER-DAEMON@locus.apache.org
To: bloritsch@apache.org



Hi. This is the qmail-send program at locus.apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
Sorry, no mailbox here by that name. (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: 
Received: (qmail 92438 invoked from network); 29 Dec 2000 14:48:44 -0000
Received: from www.saic.com (HELO cp-its-www) (198.151.15.15)
  by h29.sny.collab.net with SMTP; 29 Dec 2000 14:48:44 -0000
Received: from apache.org (fw.infoplanning.net [209.8.58.131])
          by cp-its-www (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with ESMTP
	  id GAA00016 for ; Fri, 29 Dec 2000 06:47:35 -0800
Message-ID: <3A4D4C0A.9050305@apache.org>
Date: Fri, 29 Dec 2000 21:44:26 -0500
From: Berin Loritsch 
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.6) Gecko/20001205
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-dev@apache.org
Subject: Impact of Force-Load [C2]
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h29.sny.collab.net 1.6.2 0/1000/N

I want to get some feedback regarding the impact on the force-load 
initial parameter.
The current functionality states that Cocoon will fail to initialize if 
the required class
is not loaded.  The impact of this is that we cannot use Cocoon if the 
class does not
exist.  It is logical for things like classloader bugs in WebSphere 
where the failure
is that important.  But what about having one web.xml file that can work 
with all
vendor's products--if the class can't be loaded it moves on.

The difference being this:
In IBM WebSphere, the Servlet Initialization will still fail because it 
can't find the
cocoon.xconf file.  In Tomcat, it will log a warning saying it can't 
find the class.
The error message will be misleading because the class is either 
unneeded, or
the failure is an Unknown Protocol Exception.

vs. the current method:
IBM WebSphere will run because it has the specified class.  Tomcat won't 
until
the entry is removed.



Mime
View raw message