My opinion was similar to the one stated by Emmanuel and thus my advice to Andreas... I agree that a 'more usable code' is desirable (even if you are not using any DI container, it's nice to know beforehand how you should create an object) but only as long as we don't have to call the needed changes "tweaks" :-)
2010/4/20 Guillaume Nodet <[email protected]>: > I somewhat disagree. I agree we should not be spring specific (i.e. > including specific annotations or interfaces), but providing setters or > cleaner init methods should be considered in order to make the code more > usable. > > On Sat, Apr 17, 2010 at 09:47, Emmanuel Lecharny <[email protected]>wrote: > >> On 4/7/10 2:06 PM, David Latorre wrote: >> >>> Hello Andreas, >>> >>> I don't think this has been discussed for MINA3 yet but it should be >>> sometime in the future. For Mina 2.0 I guess your best option would >>> be to write wrapper classes - and you can provide patches for these, >>> of course. >>> >>> >> IMHO, and regarding to the recent past, we should never tweak the code in >> order to make it Spring ready. The reason is that in 2011, August Framework >> will get out, meet its audience, and make geeks asking about August >> integration... >> >> The wrapper approach is the way to go. We could provide a specific jar >> containing all those Sping wrappers, then next year an other one for August >> support, before leaves start to fell... >> >> >> -- >> Regards, >> Cordialement, >> Emmanuel Lécharny >> www.nextury.com >> >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com >
