The unit test coverage in ib2 isn't stellar, but it should cover those areas well enough. iB3 fixes both issues. IMHO, 595 shouldn't add an option, it should just always be null. but unfortunately the only way to do that is to proxy the parent object.
clinton On Sun, Jun 7, 2009 at 12:01 PM, Kai Grabfelder <nos...@kaigrabfelder.de>wrote: > Hi there, > > there are currently two issues regarding lazy loading in iBATIS 2.3 (both > with patches) > > https://issues.apache.org/jira/browse/IBATIS-595 > https://issues.apache.org/jira/browse/IBATIS-596 > > IBATIS-596 adds a new feature that allows to specify within the result map > if null or a proxy object should be > returned if a foreign key is null > > IBATIS-595 fixes an issue with CGLIB and protected method access. > > I'm a little but unsecure if I should apply the patches or not as I've > never used ibatis with lazy loading > (lazy loading in hibernate was the reason why I switch to iBATIS in the > first place ;-)) and don't have any > experience with it therefore. I verified that the patches doesn't break > anything but I'm not sure if to > apply. What do you think? > > cheers > > Kai > >
