Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (athena.apache.org: domain of ole.trenner@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <46D1A357.6070401@gmx.de>
Date: Sun, 26 Aug 2007 17:59:19 +0200
From: Ole Trenner <ole.trenner@gmx.de>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: user-java@ibatis.apache.org
Subject: Re: Question about Abator
References: <12311608.post@talk.nabble.com>
 <5EBE57594E74E84DB1DC6BA8E279389D0575DD3C@SOS-MAILSRV.ascindia.com>
 <12311906.post@talk.nabble.com>
 <c593b8750708240640w7c53f731wa125b879abc84e8f@mail.gmail.com>
 <12323703.post@talk.nabble.com>
In-Reply-To: <12323703.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

NehaP wrote:
> The xml files, DAOs and particularly the Example file generated by Abator
> are very useful, hand-coding these would be more difficult than having them
> generated by Abator. The flexibility of Abator is limited only due to the
> fact that we cannot specify a custom Model bean. If we could, then giving
> Abator the mapping between the custom bean and the existing database columns
> would be as tough as simply specifying a resultMap in an SQLMap file (and
> not as tough as writing the whole SQLMap file itself).


In what way do the abator generated model classes differ from yours?

If only the property names are different, you can configure every
property using columnOverride or columnIgnore statements.

If abator just adds code you don't wnat to see, you might consider
inheriting from the abtorgenerated model classes.

If abator ignores your own inheritance scheme, you can set a base class
for your generated model files.

Cheers,
Ole.