posted 14 years ago
I'll be honest...I've only tinkered with Seam a tiny little bit. So I'm probably not all that qualified to answer your question.
That said...The new annotation-based Spring @MVC is so very simple and yet very flexible. It's certainly different than Seam. But I can't imagine it being more difficult than Seam.
For example, just to give a taste of what can be done in Spring @MVC, here's how you might write a simple controller class:
This controller will respond to requests for "/product/{productId}" requests, use a service to lookup the product information, place that information into the model, and then direct the request to the "productPage" view. Simple enough...and kinda RESTful at the same time.
As for the view itself, that's a job that falls to a view resolver. Depending on the request, that view resolver could produce an HTML, JSON, XML, Atom, RSS, or some other view output.