Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <40DC01F8.3000901@apache.org>
Date: Fri, 25 Jun 2004 12:44:08 +0200
From: Sylvain Wallez <sylvain@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
 rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Throwing errors in component's initialize() method
References: <5E091A68F794974CAF431CA31F5AF2CC11E94A@server.bizzdesign.nl>
In-Reply-To: <5E091A68F794974CAF431CA31F5AF2CC11E94A@server.bizzdesign.nl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bart Molenkamp wrote:

>Hello,
>
>I've written a component which uses native code. Therefore it needs to
>load native libraries (I do this in the initialize() method) and when
>something goes wrong with that, Errors get thrown (e.g.
>UnsatisfiedLinkError). But Cocoon doesn't seem to recognize this, and it
>looks like Cocoon starts up normally. When some pipeline is invoked, it
>seems that Cocoon is going to reconfigure/initialize itself, resulting
>in even more errors (e.g. HSQLDB that is already started, etc.)
>
>Is this the desired behaviour? Should I catch any error and rethrow it
>inside some exception, so that Cocoon correctly handles the failure? Or
>is there any way that Cocoon can catch these errors?
>  
>

Cocoon catches only Exceptions, and not Errors. So the best way is what 
you propose: catch the Error in your initialize() and retrow it, 
cascaded in an Exception.

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }