Em Wed, 23 Dec 2009 10:14:53 -0200, Alessandro Bottoni
<alexbott...@gmail.com> escreveu:
As a newbie, I have to say that learning Tapestry (5) is actually a
little bit more complicated than what you could expect after having read
the available "marketing" documentation.
This is a known issue.
Maybe this (apparently steep)
learning curve has kept the "masses" of developers/users away from
Tapestry.
You can use Tapestry almost without using Tapestry-IoC, so I don't thin
BEWARE: I'm not saying that Wicket /is/ better or more complete than
Tapestry. I'm just saying that Wicket is /presented/ (or /offered/) to
the public in a better way.
I think you're probably right.
I do not know if the IoC container is the real and sole source of the
scarce appreciation of Tapestry (if even exists such a scarce
appreciation) but... see below.
I don't think so.
I'm afraid you are right: /this/ seems to be the main, real weak point
of Tapestry. I do not know Tapestry well enough to have a solid opinion
about this topic but it seems to me quite evident that writing an
integration module is somehow (much?) more difficult than it should be.
I think you're looking for the cause in the wrong places. I guess these
integratiosn weren't written just because, unfortunately, Tapestry is not
very well-known, so few people use it and write extensions and
integrations. Or Tapestry users didn't have the need to write them. The
recentness of Tapestry doesn't help either.
Take a look at the t5-restful-webservices project written by Bill
Holloway:
http://code.google.com/p/t5-restful-webservices/wiki/GettingStarted. It
implements JSR 311: JAX-RS: The JavaTM API for RESTful Web Services for
Tapestry. Take a look at the sources. Just three classes, none of them
large. Spring integration has a small number of lines of code. 11 kb
total. There's integration with Tapestry Spring Security. It isn't hard,
people haven't had the time or need to write them.
I wonder: is it possible to improve the existing integration mechanism
of Tapestry (that is: the existing IoC container)? How?
It would be better to discuss actual integration problems and them attack
them. If anyone has already had them, please post they here.
Or should we replace it with a different/new one? Which one?
I don't see any reason at all to replace it. If it has shortcomings, let's
fix them! :)
--
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
