This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
JSF is a component based framework. A web framework came into play to ease up the web app development, to make all your code clear and readable, and so and so. Why on the earth you want to mess up all, JSF with DB? Do you like spaghetti alot?
Also our book - "JSF: The Complete Reference" covers building database or persistence architected apps with JSF. -Chris
Joined: Aug 15, 2004
In most cases, its not recommended to create data service objects, like ResultSets and RowSets, directly in your backing beans. For small apps it works well. Whereas using a separate class, which is an implementation of the Data Table Gateway pattern [Fowler, Enterprise Pattern Architecture], is more flexible because you can unit-test it and reuse it within different backing beans.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com