Davanum Srinivas wrote:
>
> Berin,
> Any thoughts? Should we fix this now?
We should not remove the "throws ComponentException" in ComposerGenerator,
or similar classes. That would preclude the Component from functioning as
it should.
>
> Thanks,
> dims
>
> --- Peter Royal <[EMAIL PROTECTED]> wrote:
> > 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]
> >
>
> =====
> Davanum Srinivas, JNI-FAQ Manager
> http://www.jGuru.com/faq/JNI
>
> __________________________________________________
> Do You Yahoo!?
> Get personalized email addresses from Yahoo! Mail - only $35
> a year! http://personal.mail.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
