From cocoon-dev-return-13942-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org Mon Jun 04 16:13:33 2001 Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 41214 invoked by uid 500); 4 Jun 2001 16:13:22 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 40928 invoked from network); 4 Jun 2001 16:13:11 -0000 Message-ID: <3B1BB31C.7DB7F35A@apache.org> Date: Mon, 04 Jun 2001 12:11:08 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: ComposerGenerator compose method notthrowingComponentException References: <5.1.0.14.0.20010604113538.020150c8@pop> <5.1.0.14.0.20010604115739.02042468@pop> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Peter Royal 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 No. The compose() method is a perfectly valid location for looking up components. There is no real preferred location of where you lookup the components you need. You do need to remember to release() the components when you no longer need them. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org