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 -> [EMAIL PROTECTED]
managing partners, inc. -> http://www.managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
