It shouldn't. The contract with the Component's interface is that the interface is all inclusive. No lifecycle methods should be part of it.
> -----Original Message----- > From: Vincent Tence [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 09, 2002 10:18 AM > To: 'Avalon Developers List'; [EMAIL PROTECTED] > Subject: RE: DataSourceComponent extending Configurable > > > Second thought, it's hard to change cause it would break > backward compatibility ... > > > -----Original Message----- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > Sent: Monday, September 09, 2002 09:46 > > To: 'Avalon Developers List' > > Subject: RE: DataSourceComponent extending Configurable > > > > > > You mean the interface extends Configurable? > > > > That is a bug. I can't believe I put code in there like > that! Unless > > another well meaning person did it.... > > > > > -----Original Message----- > > > From: Vincent Tence [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, September 06, 2002 5:43 PM > > > To: 'Avalon Developers List' > > > Subject: DataSourceComponent extending Configurable > > > > > > > > > Hi Berin, > > > > > > Any special reason why DataSourceComponent extends Configurable - > > > rather than JdbcDataSource implementing Configurable? I > came accross > > > that when implementing a mockobject DataSourceComponent. > > > > > > Vincent > > > > > > > -----Original Message----- > > > > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > > > Sent: Friday, September 06, 2002 16:59 > > > > To: 'Avalon Developers List' > > > > Subject: RE: Opinions from JUnit mailling list on Avalon > > > > > > > > > > > > > From: David W. [mailto:[EMAIL PROTECTED]] > > > > > > > > > > Ho ho. [EMAIL PROTECTED] is me ;). Although the > > > project I was > > > > > working on is still halted until I get around to > > setting up a JMS > > > > > service in Phoenix. Otherwise Avalon seems to work -- > > provided, > > > > > that is, that you're willing to go through stuff only > > > available in > > > > > CVS to figure out how to use it. > > > > > > > > Well, if you have some sort of time compression device > > > where I would > > > > be able to put 16 hours of work into an 8 hour period, I > > > would be more > > > > than happy to resolve these issues. > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Berin Loritsch" <[EMAIL PROTECTED]> > > > > > To: "'Avalon Developer's List'" > <[EMAIL PROTECTED]> > > > > > Sent: Friday, September 06, 2002 9:33 AM > > > > > Subject: Opinions from JUnit mailling list on Avalon > > > > > > > > > > > > > > > > > > > > > > From the thread entitled: > > > > > > "[junit] Unit testing multithreaded network code" > > > > > > > > > > > > (which by the way is an interesting read for testing > > > > > networking code) > > > > > > > > > > > > Had the opinions posted from two developers: > > > > > > > > > > > > "The general issue of how to approach this sort of > > > issue remains > > > > > > unsolved, but I sidestepped my own problem by passing the > > > > > > responsibilty of verifying the robustness of code to > > the Jakarta > > > > > > Avalon project. I may be taking the lazy way out, but I > > > > trust the > > > > > > Apache people to write working software." > > > > > > > > > > > > From: weitzman_d > > [mailto:[EMAIL PROTECTED]] > > > > > > > > > > > > The response was: > > > > > > > > > > > > "This might be a deceiving attitude at best. The Avalon > > > > > project has a > > > > > > high code quality indeed, but as for Jakarta projects in > > > > > general this > > > > > > does not hold. > > > > > > Just look randomly around and you'll find lots and lots > > > > and lots of > > > > > > really > > > > > > bad code with zero tests with no regard to object-oriented > > > > > principles > > > > > > and > > > > > > which violates almost any heuristics for good code > I know of." > > > > > > > > > > > > From: Johannes Link > [mailto:[EMAIL PROTECTED]] > > > > > > > > > > > > > > > I think we have a reputation for quality--which I would > > > like to see > > > > > continue. > > > > > > > > > > > > > > > -- > > > > > To unsubscribe, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > > For additional commands, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > > <mailto:avalon-dev-> [EMAIL PROTECTED]> > > > > For > > > > additional commands, > > > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > -- > > To > > unsubscribe, e-mail: > > <mailto:avalon-dev-> [EMAIL PROTECTED]> > > For > > additional commands, > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: > <mailto:avalon-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe, e-mail: > <mailto:avalon-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
