[wildfly-dev] Put MyFaces JSF into WildFly?

[ssilvert at redhat.com]

I should have added, I personally have no problem supporting both in EAP
if that's what we decide to do.

JSF is kind of unique in that for many years there have been two
well-accepted implementations.  Both have their strengths and
weaknesses.  Neither is going away.

So the upside of shipping both is that we would be the only ones
providing a choice.  Developers could even defer their choice of
implementations until after their application is finished.  Then pick
the one that runs best for them.

On 7/8/2013 2:50 PM, Andrig Miller wrote:
> 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
>>