Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I used GWT and Tapestry back in 2008. It worked well and was quite easy to setup. I am doing a Tapestry project myself at the moment so I am quite into it.</p> <p>I found the Spring IOC to be quite easy to understand and learn. You should be capable of learning the basics in well a weekend or so.</p> <p>Tapestry by the other side is a bit harder to master but much more rewarding. The tapestry IOC is also reuseable in many other environment and I use it for simple non-web related projects too. The <a href="http://tapestry.apache.org/user-guide.html" rel="nofollow">Tapestry Documentation</a> is way better these days. Also the <a href="http://jumpstart.doublenegative.com.au/jumpstart/" rel="nofollow">Jumpstart Demo Application</a> of Tapestry is very good in explaining and testing the basics and more advanced topics.</p> <p>The advantage of tapestry is, it is easy to use once you understand it. I find myself easily to dive into the source code and have not much of a problem to understand it. I dislike the services being proxies in the first place. But its more a taste. </p> <p>Also note that tapestry never got the momentum it deserved. And of cause get familar that the @CommitAfter mechanism in Tapestry is as broken as it was back in 2008 and I was not able to get those people in charge to fix it. (I tried lately and failed again). </p> <p>The rest of tapestry is a joy to use.</p> <p>Spring on the other hand has lots of business support and tons of information. Also it is widely used in the Java world. So if you get into it you have a strong asset for your professional resume.</p> <p>So in the end you are free to choose. My heart says go for Tapestry but my brain says Spring wins. Since following your heart makes you happy but following your brain makes you well more successfully, the answer is clear. Spring wins hands down. But spare some days and try out Tapestry as well. Especially the Tapestry IOC is a very reusable tool that might get handy everywhere in your daily programmer life.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload