Today's episode from the JavaOne pavilion
features Chris Richardson talking about his upcoming sessions and his opinions on Spring vs. JEE. Iyer talks about open-source Terracotta penetration. Kito Mann tells us why JSF is better than Wicket. Also, a walk through the vendor pavilion and cool Java-based robots.
because they cannot realise that spring is just a glue layer of the JEE specs (a perfect elegent glue in fact)
AND JSF cannot be better than wicket,noway,if u said that,u didnot tried wicket
DEAR GOD!!! STOP, TSS!!! STOP!!!
Spring is not and never will be a replacement for JEE. It is a complement, an enabling technology, and a potential replacement for certain aspects of JEE in certain cases. But come on now, I can expect random posters to continue this nonsense, but the video blogger? This is just getting ridiculous. I'm seriously questioning credibility now.
For details on how I feel about it, check my post on the recent "Spring is the new JEE" post. A more ridiculous, inflaming title couldn't be imagined. And I use Spring on a daily basis.
Is TSS that desperate for hits that it's resorting to these kinds of tactics? Shameful.
Well since "EE" is a set of API specifications (not an implementation) then surely Spring IS essentially a replacement for EE since its primary role is a unified set of "btter" APIs for most of the stuff one normally associates with EE (service location, persistence, security, remoting etc) ?.
Spring vs JEE and JSF vs Wicket is all about people trying to keep things simple. The problem with JEE is that it is big and bloated, you never need all of it, it is difficult to manage, and because it is NOT an implementation, mileage varies between vendors.
The problem I see with the Spring folks is that they will not stop the escalation of the things they want to replace. My prediction is that Spring will eventually become as complex and bloated as the thing (JEE) it was designed to simplify.
As for JSF and Wicket the comparison is just not warranted. Wicket makes components out of HTML elements while JSF is just a specification for any old type of component. Use Wicket if your happy working with HTML elements (lots of people are) and JSF if you are looking to use out of the box components produced by a vendor. Again, JSF may be too complex where a simple implementation can be used for lots of applications. If you look at Oracles new Rich Client Faces you can see the promise of JSF but again, its JEE of web delivery techniques. Fact is you will not get much mileage Wicket without becoming good with one of the AJAX frameworks.