ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashok Madhavan" <ashok.madha...@gmail.com>
Subject Re: Abator rootClass question
Date Thu, 10 May 2007 11:44:34 GMT
Hi Meindert,
those columns which i had mentioned are common across all tables. Having a
common base class also helps as i can reuse a lot. The other important thing
i gain is alongwith namespaces and spring support it is possible to have as
less code as possible. My action classes, DAO, DAO impl wont change at all.
it will be a common action, common dao, common dao impl. Only the namespace,
DTO, xml, jsp fill will vary. And the namespace will be injected thro
spring. this sorta nicely rolls up. when i need a specific thing which is
differnt for a particular entity, then i extend the base Action class and
add a method and corresponding iBatis chunks.


On 5/10/07, Meindert <meindert@pastelebusiness.com> wrote:
>  Not to be nasty but wouldn't it be better to normalize the database and
> put createBy, createDate, modifiedBy etc in his own table/class?
> That's what I like about ibatis, I will only fetch this kind of data when
> I actual going to use it.
> On 5/9/07, Ashok Madhavan < ashok.madhavan@gmail.com> wrote:
> > Hi all,
> >
> > i want to have a common super class for some of my data objects. this
> will
> > contain common info like id, createdBy, createdDate, modifiedBy,
> > modifiedDate etc.
> >
> > Abator does give a option called 'rootClass' in which u can specify
> this.
> > But Abator creates new setter and getter instead of just using hte super
> > classes's methods.
> >
> > is there a way by which we can tell Abator to use the super's methods
> when
> > it is present in the super.
> >
> > regards
> > Ashok
> >

View raw message