On Jan 29, 2008 12:30 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> On Jan 28, 2008 5:47 AM, HHB <[EMAIL PROTECTED]> wrote: > > > > Hi. > > Why Tapestry5 came with its own DI container? why not using Spring or > Guice > > as the default container? > > What are the advantages of T5 DI container over Spring & Guice? > > Because those containers are broken or limited. Like T5 DI would be broken or limited in a year's time when working on T6 starts. Then a whole rewrite would result out of that. And as the music goes, it won't be backward compatible. > > > > One more thing: > > Will Tapestry be rewritten for Tapestry 6? > > Possibly, but not by me :-) T5 has been designed from the ground up > to support future releases with excellent backwards compatibility. Excuse me, future? Do you know what the future holds? Didn't you make that same statement when creating T4 which again was not backward compatible? I get scared with such comments. > > This is as good as it gets! > > > Thanks you. > > -- > > View this message in context: > http://www.nabble.com/Basic-queries-about-Tapestry-tp15135666p15135666.html > > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
