On Fri, 04 May 2012 10:57:57 -0300, Vladimir Bauer <vba...@slb.com> wrote:
Dear experts,
I'm no expert, but hi! :)
Reading introductory
chapter<http://www.manning.com/leroux/leroux_meap_ch01.pdf> of his book,
I had a picture that anything relying on Java EE is dying technology (or
author wanted to create such picture of his reader)
Java EE is a huge set of technologies. The Servlet API is just one of
them. So is JDBC. For years some people say that Java is dying, but is it?
Quoting Mark Twain, "The reports of the Servlet API death are greatly
exaggerated.". :P
Play framework is an action based framework comparing to Tapestry which
is component based.
The action-based approach is, in my very humble opinion, outdated.
In the Lasagne Architecture section, the author argues the Servlet API is
complexity and too many layers. Then it shows a picture of a Java EE with
many layers. No, Servlet API doesn't have too many layers. It's just one
layer you can use. I wouldn't separate the Servlet API from the servlet
container. Regarding layers, the API and the container are a single layer,
not two separate ones. In addition, you can pick which layers you want.
You can have a Servlet API-based webapp written with a single layer (I
don't recommend it, of course). The author is contradicting himself in a
short section.
I'd like to address a question, but not in terms of what is better,
rather this one:
Is it really anything based on servlet api, Tapestry for example, is a
dying technology?
Short answer: no.
Long answer: Java has changed very little in the last 5 or 10 years. Does
this mean it's dying? If yes, Play (and anything else based on Java) is
also dying because Java is dying.
Java is still in the top 2 of the most used languages (source:
http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html). It's
mostly used for server-side stuff. In server-side stuff, probably most of
it is web apps. Web apps in Java are almost all written based on the
Servlet API directly or indirectly. In addition, Tapestry could be adapted
to be run without the Server API without any changes to existing
applications (unless they use the Servlet API directly, which is
discouraged and not needed in 95% or the time anyway).
Tapestry isn't dying because it has a very nice community and committers
that all together make the framework evolve and get getter.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, 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
