Some remarkable thing that I see more often is that authors try to make it
sound like they're talking specifically about unique JSF disadvantages,
while many of the items are actually about any-server-side-framework.
The not working with existing standards is a bit weak if you ask me,
specifically pointing out JSTL. JSF works fine with CDI, BeanValidation,
Servlets, EJB, JPA and what have you, and actually it does work with JSTL
(Facelets re-implements it really, but that's more of an implementation
detail).
On Mon, Feb 22, 2016 at 1:15 PM, Josh Juneau <juneau001_at_gmail.com> wrote:
> This person (the editor-in-chief of ServerSide) must be a JavaScript fan.
> Not to say that JavaScript is not the correct solution in some cases, but
> badmouthing an excellent and proven framework to justify the case for using
> JavaScript is not the best tactic. It does look like Cameron also wrote a
> JSF book recently...which is why this article confuses me a bit.
>
> http://www.amazon.com/JSF-2-0-Made-Easy-Development/dp/1450759300
>
>
>
> Josh Juneau
> juneau001_at_gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/index.php/author/author/view/id/1866
>
>
> On Sun, Feb 21, 2016 at 6:31 PM, Cagatay Civici <cagatay.civici_at_gmail.com>
> wrote:
>
>> Hi,
>>
>> I came across a new anti-JSF article.
>>
>>
>> http://www.theserverside.com/feature/Five-drawbacks-to-choosing-JSF-as-your-web-application-framework
>>
>> Sadly, I cannot find a way to comment.
>>
>> Regards,
>>
>> Cagatay Civici
>> PrimeFaces Lead
>> PrimeTek Informatics
>> www.primefaces.org
>>
>>
>