Clinton, thanks for the reply. I've completed the type handler
implementation. For me, the type handler is specific to one class,
which happens to be an enum. For better encapsulation, I made the type
handler a static class inside the enum class file. Everything works fine.
But that got me
No, that's actually correct. If you specify the JDBC type in the type
handler, then you have to specify it in the result map. However, if you
don't specify the JDBC type in either, that should work too, but will
override ALL string types (for example).
The reason is that iBATIS doesn't introspec
I'm new to iBatis and writing my first type handler to map a database
column to an enum whose underlying type is integer. I've got it working
after falling prey to some Java limitations (can't extend enum, can't
define static methods in interfaces, the combination of which seems to
prevent me
