Hello everyone,
I'm new here, but either I don't understand ibatis internals or you have a
design problem. First, let me share my understanding of how ibatis handles
mapping of result sets to beans:
In *ResultSetHandler.getRowValue() method you create object instance using
objectfactory. then
What you're trying to do with ObjectWrapper is beyond its intended use. It
was never a consideration nor an intention for the ObjectWrapper to
instantiate objects. ObjectWrapper was originally implemented to support
Scala types, and perhaps to support a custom property naming convention or
some
Yes, iBATIS has a mechanism that allows you to do what you want to do. It's
called Hibernate.
https://www.hibernate.org/
Enjoy.
On Wed, Feb 24, 2010 at 8:11 PM, Alexei Sokolov alexei.soko...@gmail.comwrote:
Well, Microsoft Office has Excel, which is a good spreadsheet. Does ibatis
has a
LOL... sorry I thought that was funny. :-)
But really, you're really polarizing this discussion with broad criticisms
of how our software is designed. It's hard to comment on your needs or to
help you.
I'm not exactly sure what you're trying to do, but you're digging pretty
deep into the guts
Clinton,
Sorry, I did not mean to criticize the framework. I'm just wondering if I
understand how you do things, and if the code can be improved upon.
What I see so far is that I cannot separate object construction mechanism
from the client view of the object. Think StringBuilder/String in java,
