This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
An ERP application contains more than 400 screens.. And frequent DataBase hits. In this situation may I proceed with JSF implementation..
If i proceed with JSF means what are all the points i should follow...?? Please suggest me...
If you have 400+ screens, one of the most important things you'd need to do is organize the webapp resources well. But that's true regardless.
JSF has no limit on the number of screens it can process. Likewise, since JSF has no built-in database component, the restrictions on database performance are entirely up to the persistence layer that you provide.
I would be more concerned with whether or not the overhead of JSF would be prohibitive. With that many screens, there's a likelihood of a high number of users and I've never gotten much in the way of stats on that myself, since most of the apps I do have a relatively low number of concurrent users.
However, the one thing that is good about JSF is that it doesn't require a "do or die" approach. If you implement a system and certain JSF screens demand too much in the way of overhead, you can convert them to an alternative presentation framework such as Struts or JSP/Servlet without having to rewrite the rest of the webapp.
An IDE is no substitute for an Intelligent Developer.
Joined: Sep 21, 2011
Thanks a lot..! Now i got some what clear idea.. :-)