> Well we did deprecate the Component interface many many months ago. We
> were not very good at jkeeping you folks on board and in step :-(
Uh ... actually, I think it shows considerable hubris on the part of the
Avalon group to assume that they can deprecate and then break an API within
a YEAR, much less a few months.
> careful depecation scehdule in Avalon-Framework and then
Avalon-Cornerstone.
With all due respect, I think that the notion of careful deprecation
schedule doesn't seem to have been fully grasped by that group. ONE DOES
NOT BREAK CLIENT CODE, especially on such a short schedule.
> your users are far smaller in number that those to say Servlet
> (or those to say jdbc - a real balls-up of backwards compatability)
I've migrated JDBC client code and servlets for several years now without
having to change them. Yes, there are some peripheral nuances, but what
core issues have you had? The biggest screwup I've had with Sun was with a
change to JSP that broke a lot of pages, but they have fixed it in JSP v2.
In any event, this is all water under the bridge. The Avalon project did
what it did, and we're all stuck with it.
setMailStore(MailStore mailStore)
setDataSourceSelector(DataSourceSelector selector)
That begs the question: what is a MailStore interface, or a
DataSourceSelector interface? And what about other interfaces (e.g.,
repositories)?
And keep in mind that so far Danny has been against anything not in
JavaMail, java.* or Mailet API. I'm arguing that Jakarta Commons ought to
be OK, too.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
