At 10:11 10/4/01 +0200, Leo Simons wrote: >proposal: >For 4.0 of the framework code, CascadingException >is updated to extend RuntimeException,
-1 Whats wrong with CascadingRuntimeException??? >and new exceptions >are created for all lifecycle methods except run(), stop() >and dispose(). -1 for run +1 for stop/start/resume/suspend/etc +/-0 for dispose() (it will be ignored anyway) > >So: >contextualize() throws ContextualizationException How about ContextException? >init() throws InitializationException how about initialize() throws InitializationException ? ;) >For: >- making use of RuntimeException means that existing code > will be able to compile and run if the exceptions are > not actually thrown. Short term benefit is not worth the long term negative effects IMO >- since the lifecycle exceptions are indeed (almost > always) runtime exceptions, this setup is also > correct. What makes you so sure. I have gone out of my way to make all lifecycle exceptions not RuntimeExceptions ;) >- does Cocoon2 have the time to update to this before the > beta? (if not, I propose the same change for 4.1) Should have. Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
