Agreed! There could always be more improvements.For same resultsets and same column names and same bean properties like situations, I think a good approach is to use qualified names. I mean use the name spaces that you define your sql map files. Then you will always get to the particular culprit i
Debashish,
I can see where you are coming from, but there are some situations where
iBATIS is not as well-behaved.
Situations where iBATIS error messages are not very helpful include
basic things like a typo in the XML(a missing quote, or close tag), in
which case the parser goes completely ber
Hello TedAbsolutely! I completely agree with you. I was actually replying to Vadim's email rather than yours :).First few days are always difficult and a list of most frequently committed errors/mistakes and their resolution would surely make it more popular.
-DebasishOn 7/19/06, Ted Schrader <[EMA
Hi Debasish,
You make an excellent point that iBATIS does give specific error
information in these situations and, now that I have more experience
with the tool, the examples you provide seem pretty straight-forward
in their resolution. And, as you mentioned, turning on the logging
can be a life
I would opt to disagree.Following the suggestions would surely help. You can also put logs for iBATIS. There are many email threads about that.I have made many minor to major mistakes in the sql-map files and have been pointed quite well by iBATIS.
E.g. I do get logs like thiscom.ibatis.common.jdbc
Hi Vadim,
I feel your pain in quietly cursing iBATIS' seemingly mystical error
messages when I was first starting out.
I'm not aware of any way to make iBATIS' error mechanism more verbose.
In practice, I do the following, along with your suggestion of
commenting out parts of the map:
1. Keep
Hi all,
in a situation where iBATIS's parser throws an exception, is there a way
to tell which part of the sql map being parsed is actually the culprit?
The error shown in the exception is too vague, and doesn't point to a
particular file/line/xml element/whatnot. Specifically, I have a case
