Hm, I don't understand the internals well enough to really understand that.
Sure name resolution is table specific?!
To work around the issue for my specific use case I patched this method in
Reflector:
public String findPropertyName(String name) {
String propertyName = caseInsensitivePro
I decided not to go there. It created new challenges. That's not to say it
can never be there... but it's not as easy as it looks. The biggest problem
is with columns like "id", where multiple tables use the same column name.
But that's just one challenge...
Clinton
On Tue, Nov 10, 2009 at 4:
Any news on this?
I haven't found any pluggable name resolver in 3.0 (Beta 5)?!
This would make my SQL much shorter and more readable (omitting all those
aliases).
Clinton Begin wrote:
>
> This is definitely something I've wanted to do for a while. Version 3
> will
> have a property/column nam
Docs are wrong, I've removed that parameter...
It's now just lazy loading enabled/disabled. You need CGLIB for lazy
loading now... without exception.
Cheers,
Clinton
On Tue, Nov 10, 2009 at 11:54 AM, masonka...@libero.it wrote:
> Hi,
>
> I have a problem with last two ibatis beta version abou
I am running a stored procedure that returns 2 cursors and none of them have
any data. I have the following mapping xml:
{ call my_sp (?,?,?) } First result set
is being put in a HashMap...second resultSet is being put in a `MyBean`
class. code in my DAO follows: HashMap map = new Hash
Hi,
I have a problem with last two ibatis beta version about configuration
file (4 and five one).
It seems that framework doesn't know the
"enachementEnabled" ()
configuration tag, but it is in the documentation.
I controll and it is right
written.
The error is
Exception in thread "main" org.
Hi All,
Please if possible could someone assist me, I have been banging my head on
this problem for near a week now and this is holding my project up
seriously. I have tried everything I can think of and everything I can find.
As soon as I include the composite key mapping of
column=”{prop1=col1,
That is a little odd. It looks like I intended for something else there.
I'll look at it.
Clinton
On Tue, Nov 10, 2009 at 8:09 AM, Poitras Christian <
christian.poit...@ircm.qc.ca> wrote:
> What is the expected behaviour when calling dataSouce.getConnection() for
> managed transactions in iBAT
What is the expected behaviour when calling dataSouce.getConnection() for
managed transactions in iBATIS 3?
I find suspicious that ResultLoader calls dataSouce.getConnection() at line 89
which could create an unexpected connection. And since managed transaction is
used, the connection may never
