No matter how good a framework is, it can always be used incorrectly. This holds true for JavaServer Faces (JSF) as well as any other framework.
In this session, we'll look at real-world examples of antipatterns for developing JSF applications. These range from specific issues, like hard-coding component IDs in backing beans and accessing the database in getter methods, to more systemic problems, such as lack of common-sense standards and usage of the wrong APIs. Along the way, we'll discuss best practices that will help ensure that your JSF applications are performant, well-designed, and easily comprehensible to new team members.
Author:
Kito Mann
Kito D. Mann is the Principal Consultant at Virtua, Inc., specializing in enterprise application architecture, training, development, and mentoring with JavaServer Faces, HTML5, portlets, Liferay, and Java EE technologies. He is also the editor-in-chief of JSFCentral.com (www.jsfcentral.com), co-host of the Enterprise Java Newscast (http://www.enterprisejavanews.com), host of the JSF Podcast interview series (http://www.jsfcentral.com/resources/j..., and the author of JavaServer Faces in Action (Manning). Mann has participated in several Java Community Process expert groups (including CDI, JSF and Portlets) and is also an internationally recognized speaker. He holds a BA in Computer Science from Johns Hopkins University.