Lutz, Having seen some discussions in the past about the history of Tapestry, I'm wondering what the status of Tapestry with CDI support will be. In other words, is it again going to result a new major release incompatible with previous versions? I think CDI in it's current form, if should be supported, would require some fundamental changes to the core of Tapestry's IoC that would definitely result in API break. At least the Spring guys also say so about their framework.
I have an idea, may be a controversial one. I've seen much about Tapestry and think it's a nice Framework. But what I still don't understand is why it's not widely in use. It existed before Wicket but Wicket is far more popular. I don't think it's only because it's users are very vocal. There is also a saying that a good product sometimes sells itself. My proposition is why not let Tapestry and Wicket join hands, migrate some of the nice ideas to Wicket and lets try to go standardize Wicket as a JSR. Again, I know this is a controversial proposition that might result in some immature ones labeling and calling me names, as I've seen in the archives. On the other hand I know there are wise and intelligent ones in this community who would offer constructive arguments. It is these group of people that I'll consider serious. Gerald 2009/12/23 Lutz Hühnken <lh.tapestry.l...@googlemail.com> > Hi everybody, > > I think the discussion on TheServerSide actually is somewhat > interesting, but not because of the unfortunate Tapestry vs. Wicket > flame war. Let's have a look at the topic leading to that... > > - One part of Java EE 6 is "CDI" (JSR 299) - > http://jcp.org/en/jsr/detail?id=299 - originally called "Web beans". I > think it was inspired by Gavin Kings Seam Framework. > > - The reference implementation for that seems to be something called > "Weld" - http://docs.jboss.org/weld/reference/1.0.0/en-US/html/ > > - Weld has Wicket support build in, and the examples are given in > Wicket (although the Java EE "standard" would be JSF 2) because Wicket > is easier to learn than JSF (at least Gavin King says so in > http://in.relation.to/Bloggers/HowToStartLearningJavaEE6, but I think > many would agree with that). > > So the interesting (to me, at least) questions are: > > - How does CDI relate to Tapesty and Tapestry IOC? > > - Should / could Tapestry incorporate / conform to CDI somehow? > > - Should we try to add Tapestry support to Weld? > > - Or is Java EE 6 / CDI just not relevant to Tapestry? > > I haven't really looked at Web Beans resp. CDI yet, but from first > site, it defines some context scopes (request, session, application, > conversation) and some annotation based dependency injection. > Both areas are already covered by Tapestry (although afaik there is no > conversation scope (yet) in Tapestry). > > So are CDI and Tapestry mutually exclusive? Or should Tapestry be > refactored to use standard CDI annotations, so it can claim to be a > CDI / JSR 299 implementation? > > I would love to hear your opinions about that. > > Regards, > Lutz > > > > > -- > altocon GmbH > http://www.altocon.de/ > Software Development, Consulting > Hamburg, Germany > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
