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
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
In the 1.x releases, there was a XmlSqlMapValidator class that could
validate the maps at compile time:
ibatis_db_guide-1-2-9.pdf
Validation
While your developing your application, it is probably quite
inconvenient to start up your app server just to test your SQL Maps.
For this reason, a
And it sounds like this is strictly to determine if the XML is
well-formed and valid. The trick is determining if the XML matches the
DB schema, which is a far more difficult (infinitely more difficult?)
problem.
-ed
On 7/22/05, Ron Grabowski [EMAIL PROTECTED] wrote:
In the 1.x releases, there
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
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:
