Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-Id: <5.1.0.14.0.20010604115739.02042468@pop>
Date: Mon, 04 Jun 2001 12:00:18 -0400
To: cocoon-dev@xml.apache.org
From: Peter Royal <proyal@managingpartners.com>
Subject: Re: ComposerGenerator compose method not
  throwingComponentException
In-Reply-To: <3B1BAD2D.A95C94FD@apache.org>
References: <5.1.0.14.0.20010604113538.020150c8@pop>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:45 AM 6/4/2001 -0400, you wrote:
> > Is there a reason why the compose method of the ComposerGenerator class
> > does not throw a ComponentException? The Composable interface specifies
> > that a ComponentException can be throw from that method.
>
>no reason that I know of.   But you will notice that the compose method
>only stores the ComponentManager--so that you will have to trap your
>ComponentExceptions in the setup() mehtod when you actually exctract
>your components.

I've been extracting ThreadSafe components in the compose method of my 
components since the ComponentException is already listed in the throws 
clause (custom components and Actions). Is this bad form/going against the 
grain of the design? Thanks :)
-pete

-- 
peter royal -> proyal@managingpartners.com
managing partners, inc. -> http://www.managingpartners.com


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org