Re: Deprecating the DAO framework?

[Javier Urbaneja <ur...@gmail.com>]

-1
iBATIS DAO framework is easy, works great, and the DAOs are a very nice
place to manage the transactions. I liked the DAO framework since I saw it
in action at the JPetStore example.
Probably I will move on to Spring too, but I don't think every iBATIS user
has to.
IMHO, there's no reason to deprecate it, it's not like PaginatedList, which
I agree is probably confusing some people and has some shortcomings (memory
usage if it's for web applications, not serializable,...). People who don't
like the DAO framework, just don't use it.
Clinton, I really think you should not be "ashamed" of that nice piece of
code and should not "erase" its existence in the project.

Greetings.

On 10/22/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Hi all,
>
> I think we should deprecate the iBATIS DAO framework for these reasons:
>
>
>    - In my opinion, the iBATIS Mapper does a fantastic job of isolating
>    the persistence layer as is.
>    - I've personally started to shy away from data access layers.
>    - For most applications, there's no big deal in having a dependency
>    on SqlMapClient.
>    - If you do use a DAO layer, I suggest Spring DAO
>    - If you can't use Spring DAO, I suggest writing your own DAO layer
>    that is as simple as possible and tuned for your environment.
>    - I don't believe very many people use the DAO framework, for those
>    that do, you can safely continue to do so.  It hasn't changed in years, and
>    so it likely won't.
>
> Deprecation would basically mean we take it off the website as a
> downloadable component and remove the doc links etc.  Of course we'd still
> answer the odd question on the mailing list, but we'd likely not adopt any
> changes and possibly not even fix any bugs (but you're welcome to take the
> source and use it under the Apache License).
>
> What do you think?  Thoughts?
>
> Cheers,
> Clinton
>
>