[wildfly-dev] Put MyFaces JSF into WildFly?

Andrig Miller anmiller at redhat.com
Mon Jul 8 14:50:03 EDT 2013


My personal opinion on this, is that we should not ship two implementations.  I know this is in the community, so it doesn't cause any issue with support as we don't have to ship both in EAP.  Having said that, if people in the community adopt MyFaces, and then move to EAP, and its not there, its just another thing that causes a problem for adoption of EAP.

Andy

----- Original Message -----
> From: ssilvert at redhat.com
> To: wildfly-dev at lists.jboss.org
> Sent: Monday, July 8, 2013 11:31:27 AM
> Subject: [wildfly-dev] Put MyFaces JSF into WildFly?
> 
> Ever since we switched from MyFaces to Mojarra I've incurred the
> wrath
> of MyFaces fans.  Regardless of the relative quality of each
> implementation, we have stuck with Mojarra because it always
> implements
> the latest spec long before MyFaces.  Now is no exception as Mojarra
> fully supports JSF 2.2 and MyFaces 2.2 is incomplete.
> 
> However, with Multi-JSF in place, it is now trivial to ship both
> implementations and allow the end user to choose which one they like
> best.
> 
> Any thoughts on this?
> 
> Stan
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 


More information about the wildfly-dev mailing list