> As I said in another thread, you're suggesting replacing Tapestry-IoC > with CDI. If that was done, people would still learn one IoC framework > in order to learn Tapestry. CDI has a broader reach (in termos of > concepts and features) than T-IoC. Not much people use CDI now (I may > be wrong, of course). Given all that, I don't think replacing > Tapestry-IoC with CDI in Tapestry would turn Tapestry much easier to > learn, if at all. And you'd need to rewrite a lot of Tapestry code, > which would need to get bigger. I don't think that's worth the effort > at all. >
As far as I know, CDI which is part of Java EE 6 is widely used in enterprise applications, I have used it in a large enterprise applications(the development cycle is over 20 months). You should keep a eye open to other communities, such as JBoss.org(in my view, it is the most active community in these years), and glassfish...and the Apache OpenEJB/OpenWebBeans related communities. I am a Tapestry4.0 user, but after 4.0, I gave up Tapestry. But I subscribed this maillist to keep up with what is new in the newest Tapestry. Of course, I rarely posted new topic in this maillist and replied others. For the new Tapestry5, I have read the code Tap5-hotelbooking which is the sample motioned in the Tapestry 5 homepage. But I was disappeared, too many artifacts are invented by Tapestry(like Tapestry4 before), such as IOC, it is stopper for me to adopt it. Tapestry should embrace the existed and mature specs, such JSR330, Bean Validation, Managed Bean, etc, Spring has supported them in 3.0 natively. CDI provides more than JSR 330(only provides DI), for example, CDI events, Tapestry can provides bridges to CDI Events, CDI conversation, which can be implemented to group Tapestry pages to process a wizard like task easily, eg. shopping cart. As I know, there are fewer people using Tapestry after 4.0, at least in the circle of my friends, it is the truth. Tapestry developers should open minds and work together with other technologies/framework, not invent everything themselves. Thus Tapestry will be back to the view of more Java developers. Regards Hantsy -- Fulltime Java EE Freelancer from China --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
