Note that there are some explanatory texts on larger screens.

plurals
  1. POSpring MVC & UI Components
    primarykey
    data
    text
    <p>I'm in the "technologies selection" phase of a small, single-page web application that will be heavily-based in AJAX, and which will report to a Java backend.</p> <p>In a previous question I posted several weeks ago, the SO community at large felt strongly that I would be better off going with a Spring MVC-based web app than with something in JSF. Since Spring is request-oriented, and JSF is component-oriented, it would only make sense to use Spring for something that is going to be getting <strong>a lot</strong> of asynchronous requests.</p> <p>If I <em>were</em> going the JSF route, then my next set of decisions would be whether or not to use so-called UI component libraries for the view technology, such as <a href="http://primefaces.org/" rel="noreferrer">PrimeFaces</a>, <a href="http://www.icesoft.org/" rel="noreferrer">IceFaces</a> or <a href="http://myfaces.apache.org/" rel="noreferrer">MyFaces</a>.</p> <p><strong>So, I'm wondering:</strong> Does Spring MVC have anything similar to, say, PrimeFaces (or its likes) for creating the view component for my page(s)? I know its not component-based, but I'm not all that familiar with Spring MVC's web platform and was wondering what are some <em>de facto</em> standards (if any) or typical technology stacks that Spring web developers use for constructing nice web pages.</p> <p>And, if Spring just uses run-o-the-mill template engines, would something like <a href="http://freemarker.sourceforge.net/index.html" rel="noreferrer">Freemarker</a> suffice?</p> <p>I guess this is a "best practices"-type question for a budding Spring web developer.</p> <p>Thanks in advance!</p>
    singulars
    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.
 

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