> 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.
C'mon. With all due respect - 'limited' would have sufficed, don't you agree?! No need to call them 'broken', right? > >> 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. > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
