Folks;
not sure whether this is a stupid question; I've been playing with this
idea before already: As far as I see, after dealing with a bunch of
other approaches (EclipseLink/JPA, hibernate, ...), I saw that in the
end parts of our backend code ended up being a weak re-implementation
of
Interesting idea - so you end up with something like this?
myEntity.id
myEntity.name
myEntity.attributes.someField
myEntity.attributes.someOtherField
You could do that, but since you're doing select * you'd have to do
it with a result map or row handler.
Larry
On Thu, Dec 17, 2009 at 1:32 AM,
Larry Meadors schrieb:
Interesting idea - so you end up with something like this?
myEntity.id
myEntity.name
myEntity.attributes.someField
myEntity.attributes.someOtherField
Yes, that's basically what it is supposed to be. Reason for this: We're,
in the backend, using a legacy (proprietary :(
Larry Meadors schrieb:
Not really a preferred way - it's going to be up to you to decide if
you want code or configuration.
I see. :)
I think a row handler might be the best option in this case. So you
would have ibatis mapping all of your results to a Map, then in your
RowHandler, you'd
