Adib Saikali wrote:
I too am trying to making a decision about using JSF or not in a productionNo, but the Problem I generally see with both frameworks is the xml navigational glue, which might be a mem drain once the application becomes bigger.
project. I building an web app that is modular with rich user interactions
and I want to run the app as an application server provider model. I highly
attracted to the component nature of JSF and the fact that JSF ships with
nice components that I can use right away.
The choice to use Java has been made but I am not sure if should be using
JSF or some other framework. Is there anything about how JSF works that will
put it at a significant performance disadvantage compared to Struts? How
would the CPU and memory profiles of JSF app compare to the same app built
in Struts?
(you can average expect 5+ navigational entries per page)
With a few hundred pages you end up with an xml file of
over thousand entries or more and that can start to be a mem drain if the framework uses dom.
Besides that both frameworks basically cry for "use tools" because programming that stuff basically ends up with having 3-4 editors open at once basically doing work side by side in all of them.
(Navigational Glue, view code, model code, controller classes, and several includes in the view which keep the main view code smaller etc...)
