« Return to Thread: Next Release

Re: Next Release

by Michael McCurrey-3 :: Rate this Message:

Reply to Author | View in Thread

I like this idea.  I run into this problem quite often myself.  A Binsor typish port wouldn't solve this, but this wouldn't be hard to do via a build-event check.

On Mon, Jun 22, 2009 at 7:16 AM, Tom Kise <TOKI@...> wrote:

 

Hi Michael

 

We have a wish for compile time check against type safety, as IBatis today will fail runtime only, if there is an error in the XML-files. It could be that is what you want to have a look at regarding number 6 on your list, but I’m not sure?

 

Best regards

TOM KISE ://
MANAGER /
DEVELOPMENT 1 /

--------------------------------------------

EMENTOR DANMARK A/S ://
LAUTRUPVANG 12 /
DK-2750 BALLERUP /
T :// +45 70 222 770 /
M :// +45 72 208 194 /
F :// +45 70 222 768 /
MAIL ://
tom.kise@.../
EMENTOR.DK

 

From: Michael McCurrey [mailto:mmccurrey@...]
Sent: 22. juni 2009 15:29
To: user-cs@...
Subject: Next Release

 

Ok folks,

I'd like to plan the next release of iBatis and would like to know "What do you want?"  I would like to make a few small releases  to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line.  Some things I want to do for 'just me' are:

1.  Feature match the Java version
2.  Fix an annoying list non lazy load bug
3.  Rev to my Castle.DynamicProxy2 patch
4.  Expose a QueryForDataTable
5.  Drop .net 1.X compatibility.
6.  Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.


--
Michael




--
Michael J. McCurrey
Read with me at http://www.mccurrey.com
http://chaoticmindramblings.blogspot.com/

 « Return to Thread: Next Release