As to why, it is because there is a large install base of iBATIS users and we have committed that the iBATIS 2.x releases will run with JDK 1.4.
As for the future, look here: http://opensource.atlassian.com/confluence/oss/display/IBATIS/iBATIS+3.0+Whiteboard Jeff Butler On Thu, May 15, 2008 at 3:38 PM, Thiago F. G. Albuquerque <[EMAIL PROTECTED]> wrote: > But... why? Is this a design decision? Are there any plans to support > generics in the future? > > Thiago > > Jeff Butler wrote: > >> Ahhh...this is far beyond the introspection capability of iBATIS. iBATIS >> is built for JDK 1.4 and will not understand these types of getters. >> Jeff Butler >> >> On Thu, May 15, 2008 at 2:11 PM, Thiago F. G. Albuquerque < >> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: >> >> Jeff Butler wrote: >> >> OK - we need to see the SQL map (just the update) and the two >> Java classes. Hopefully they are not too big :) >> >> >> I'm afraid they are :-/ And to make matters worse, all the >> indentifiers are in Portuguese. >> I can write some minimal code that reproduces the problem and send >> it to the list. >> >> But, I was thinking... maybe the problem is not the inheritance. In >> fact, all the getters in this class are inherited. What is different >> about this getter in particular is that its return type in the >> superinterface is generic: >> >> public interface BaseDomain<PK extends Serializable> >> { >> public PK getCodigo(); >> } >> >> ("codigo"(pt) == "code"(en)). >> >> Thiago >> > >
