>> interface immutability principle,
Principles are not made to be followed blindly. If they were, progress would be ground to a halt. How else are we to learn from our mistakes but to change what we've made?
Regardless...deprecation doesn't stop you from using anything. It just says: "we officially recommend you don't."
navrsale <firstname.lastname@example.org> wrote:
Although it seems straightforward and logical decision, I don't think it is a
good idea, primarily because of
interface immutability principle, which have been proven as beneficial on
many large scale projects. Once it is
published it is published, that's it (for example, in servlet specs there
are still some things dating back from 1998, and yes, I had to follow these
same old APIs on the latest platforms as recently as last year, for the
reasons which are hard to comprehand ;)
Clinton Begin wrote:
> Actually I've heard the opposite opinion. Having the DAO included in the
> same download was confusing to new users.
> A separate download (made really clear) will work well.
> On 11/3/06, Brandon Goodin <email@example.com
>> I just posted this issue that i'd like to fix for this release. It is a
>> simple fix. But, i wanted to get some feedback as to where we should
>> Also, I think we need to still make the DAO available on the site for
>> download. Except we need to mark it as deprecated and unsupported. We
>> also provide upgrade instructions to users if we aren't already going to
>> so. I can see where this move will be very confusing to some. There are
>> people who are still using the DAO including our example app.
>> On 11/2/06, Clinton Begin <
>> > Hi everyone,
>> > I would like to release iBATIS 2.2.1 by the end of the weekend if
>> > possible.
>> > It's a pretty significant release, probably more than just a
>> X.X.1release....we could call it
>> > 2.3 if you think that would be more appropriate.
>> > The changes so far are:
>> > o DEPRECATED All PaginatedList related features due to misuse, minimal
>> > applicability and inflexibility
>> > o DEPRECATED DAO Framework -- Removed from primary distribution,
>> > available as a separate download
>> > o Removed DAO framework from Subversion source tree (tagged before
>> > removal)
>> > o Changed deployment file naming convention, dropped "DBL" and
>> > lowercased all
>> > o Merged common and sqlmap jar files (no more DAO means there's no
>> > point in keeping commons separate)
>> > o Implemented transaction level PreparedStatement caching
>> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
>> > o Fixed IBATIS-353 - Probe exception when using inheritance
>> > Are there any bugs etc. that should make it into the next release?
>> > Cheers,
>> > Clinton
View this message in context:
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.