Em Wed, 23 Dec 2009 08:28:35 -0200, Piero Sartini <li...@pierosartini.de>
escreveu:
I am not sure if it is possible or not to integrate CDI without
breaking backwards
compatibility... but it is something we should find out.
Agreed. :)
I've also thought about this, and my only conclusion is that Tapestry is
too difficult to master. Especially when it comes to tapestry-ioc and
getting productive with it.
What exactly is difficult to master? I think Tapestry-IoC is easier to
learn than Spring.
Maybe there's a sensation of Tapestry being hard to master because it's
built on IoC and has many hooks to do many things. Other frameworks has
many hooks, but less ways to customize them without changing the sources
or doing difficult configurations.
If I look at Wicket or other frameworks there are lots and lots of
integration modules
for just everything. Why is that? My answer is because it is way
easier to write them.
I guess is that because these frameworks are older and people had more
time to write these integration modules. Tapestry 5 is way younger,
specially when you think that the first stable version was released in
December 18th, 2009, one year and 5 days ago. Wicket 1.0 was released in
June 2005, 4.5 years ago. That's a 3.5 years head start.
There isn't an integration with JFreeChart or JasperReports, for example,
maybe because it's so easy to write it (a page returning StreamResponse in
its onActivate() method).
But I would be perfectly fine trading the IoC container...
The day you understand distributed configuration I guess you'll change
your mind. :)
I also use Spring, and I think Tapestry-IoC is bothe easier and more
powerful.
But what exactly do you find difficult in Tapestry-IoC? What could be
easier? What could be better documented? What have you tried to do with
T-IoC and failed?
Feedback is very important and we can use it to improve Tapestry and
Tapestry-IoC. ;)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
