*cough* unit tests *cough*
*hah* need them anyway *choo*
Cheers, ;-)
Clinton
On 7/22/05, Bing Zou <[EMAIL PROTECTED]> wrote:
An easy solution pops up to my head is to write a simple class that
scan through all the xml files in sql-map-config.xml and use
reflection to verify the getter/setters etc.
I hope the future iBATIS release can include such a util.
Thanks.
Bing
On 7/22/05, Larry Meadors <[EMAIL PROTECTED]> wrote:
> Usually simply loading the sql map shows much of that.
>
> There is a property that is earmarked to show more info, but it has yet to
> be implemented.
>
> This has been at the top of my wish list for some time now, too.
>
> Just too much other crap in front of it I guess. ;-)
>
> Larry
>
>
>
> On 7/22/05, Bing Zou <[EMAIL PROTECTED]> wrote:
> > Yes, I read that thread. Unfortunately, there don't exist many unit
> > tests that directly test the correctness of the iBATIS queries. All
> > the queries have been approved by DBA and are supposed to be correct.
> > Actually, my question is not to test the correctness of the iBATIS
> > queries, but to test these:
> >
> > 1. Whether the getter/setter methods of the resultClass has changed.
> > 2. Whether the ParameterClass, resultClass has been renamed.
> > 3. Whether the setter/getters are overloaded.
> > ...
> >
> > Thanks a lot.
> > Bing
> > On 7/22/05, Ed Griebel <[EMAIL PROTECTED]> wrote:
> > > This exact question was asked yesterday or Wednesday, you can probably
> > > find the thread in the archive.
> > >
> > > -ed
> > >
> > > On 7/22/05, Bing Zou <[EMAIL PROTECTED]> wrote:
> > > > Hi all,
> > > >
> > > > We are doing a lot of refactoring and one issue came up was that
> > > > moving JavaBean, renaming or overloading setter/getters could break
> > > > the existing iBATIS queries. But we have to wait till runtime and test
> > > > every related functionality for that purpose.
> > > >
> > > > I am wondering whether there is a way we could perform this kind of
> > > > validation in advance?
> > > >
> > > > Thanks.
> > > > Bing
> > > >
> > >
> >
>
>
