Return-Path: 
 <dev-return-538-apmail-excalibur-dev-archive=excalibur.apache.org@excalibur.apache.org>
Delivered-To: apmail-excalibur-dev-archive@www.apache.org
Received: (qmail 39123 invoked from network); 29 Jul 2004 11:16:26 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 29 Jul 2004 11:16:26 -0000
Received: (qmail 98262 invoked by uid 500); 29 Jul 2004 11:16:25 -0000
Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org
Received: (qmail 98226 invoked by uid 500); 29 Jul 2004 11:16:25 -0000
Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@excalibur.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@excalibur.apache.org>
list-post: <mailto:dev@excalibur.apache.org>
List-Id: "Excalibur Developers List" <dev.excalibur.apache.org>
Reply-To: "Excalibur Developers List" <dev@excalibur.apache.org>
Delivered-To: mailing list dev@excalibur.apache.org
Received: (qmail 98212 invoked by uid 99); 29 Jul 2004 11:16:25 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [220.110.69.218] (HELO tanukisoftware.com) (220.110.69.218)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 29 Jul 2004 04:16:22 -0700
Received: from [127.0.0.1] (127.0.0.1)
	by localhost (127.0.0.1) with [XMail 1.9 (Win32/Ix86) ESMTP Server]
	id <SD8B> for <dev@excalibur.apache.org> from <leiflists@tanukisoftware.com>;
	Thu, 29 Jul 2004 20:15:49 +0900
Message-ID: <4108DC64.70902@tanukisoftware.com>
Date: Thu, 29 Jul 2004 20:15:48 +0900
From: Leif Mortenson <leiflists@tanukisoftware.com>
User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707)
X-Accept-Language: en, ja, en-us
MIME-Version: 1.0
To: Excalibur Developers List <dev@excalibur.apache.org>
Subject: D-Haven-event bug in current Fortress trunk build.
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

I did not see where D-Haven project bugs should be posted. It sounds
like the
members are the same, so this should get into the right hands :-)

If Fortress has any problems initializing any of its components then it
is designed
to call CommandFailureHandler failure. This defaults to the
FortressCommandFailureHandler but it is possible to override it with one
of your
own. (As I have done).

The current trunk build now makes use of the d-haven-event jar and this
has been
broken.

Digging into the d-haven source, I see the problem:

When the DefaultCommandManager is instantiated, it initially sets its
internal
CommandFailureHandler to an instance of DefaultCommandFailureHandler.
Then within the constructor, it immediately uses that handler to instantiate
a new CommandEventHandler.

The DefaultCommandManager class has a setCommandFailureHandler method
which is being called by Fortress after the constructor completes. But the
problem is that it is already too late to be used. So my custom handler, and
even the default FortressCommandFailureHandler is never used.

Either the instantiation of the CommandEventHandler is going to have to be
moved, or a way of changing its CommandFailureHander is going to have to
be introduced.

Cheers,
Leif

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/