Just an alternative point of view to consider: There are many more important factors to consider when choosing a framework outside of "does this look like x, which I already know about." Think about which tools are best for solving the problem, and less about what is best / easiest for you. Ultimately, if you intend to work with Java in your enterprise, you will probably have to learn a few other frameworks and move between them anyway. You can really take your project off foot if you choose JSF just because it is "like .NET."
And only because of this I seem to answer the question: in fact, there is no Java structure that approximates what Microsoft has done with .NET MVC. The whole βthing after ASP.NETβ reminds me a lot of PHP and Spring before annotation-based configuration. Again, I quit .NET in 2009, so I probably need to shut up now.
user785262
source share