Using JSF isn't enforced if using Apache Geronimo. I'd suspect that web frameworks such as Play are rather strict on which web technologies must be used. But that's exactly the difference between Play as a web framework and Geronimo as an Java EE app server. App servers are merely execution environments to run apps of different natures each using a different web technology such as JSF, JSP or a more client-orient model such as AJAX or RIA apps. It is just that Geronimo comes with out-of-the-box support for JSF and JSP (per the various Java EE specs).

Cheers
Daniel


On Thu, Jan 10, 2013 at 11:44 AM, Lochschmied, Alexander <Alexander.Lochschmied@vishay.com> wrote:
Thanks Kevan - maybe this should be under a new subject...

I am really concerned about using JSF and want to avoid it. But it seems to be the recommended way to generate your HTML.
>From what I understand, there shouldn't be any problem just not to use JSF. Instead create dynamic markup mostly with Javasript and AJAX. Please correct me if I'm wrong.

Alexander

-----Ursprüngliche Nachricht-----
Von: Kevan Miller [mailto:kevan.miller@gmail.com]
Gesendet: Mittwoch, 9. Januar 2013 16:44
An: user@geronimo.apache.org
Betreff: Re: Why should I use Geronimo?


On Jan 9, 2013, at 5:50 AM, "Lochschmied, Alexander" <Alexander.Lochschmied@vishay.com> wrote:

> Can it be compared to Play Framework for example?

Geronimo is a lighweight, composable, Java EE-based application server. A full Java EE Geronimo application server contains multiple technologies (JPA, Servlet/JSP, JSF, JMS, etc.).

I think of the Play Framework as fundamentally a Web Framework (e.g. JSF, Grails, Spring MVC, etc.). You can run Play applications in standalone mode (I'm not sure if that's what Play calls it). You can also create a Play application, generate a .war file, and deploy the .war file on Geronimo.

Hope that helps.

--kevan