At 04:10 PM 6/7/2002 -0400, you wrote:
>It seems that Peter already beat me putting a proposal Avalon 5
>directory out there. Quick question regarding the Startable
>interface:
>
>public interface Startable
>{
> void start() throws Exception;
> void stop() throws Exception;
>}
>
>Is there any particular reason that start() and stop() require
>exception throwing?
Cause they may fail? ;P
> Wouldn't RuntimeExceptions (reported in the
>javadocs so they are documented) be better?
That would suck. The only people who should be dealing with exceptions from
them is containers so I am not sure what the hassle is.
>Also, I thought that we were in favor of separating Intializable
>and Disposable. They aren't as tightly coupled as start()/stop()
>or suspend()/resume(). Otherwise, there will be a lot of components
>with either an empty initialize() or an empty dispose() method.
I think they are just as coupled as the others and would prefer to see them
merged but no real issues if they aren't.
ie I think that anytime you allocate resources you should have to think
about deallocating them.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
