Reflection by itself should not introduce a big performance hit. As Norman said, Seam uses much more reflection than JSF. Yet, in our tests, adding Seam only decrease performance by 5% to 10%.
The big performance problem in JSF is the need to serialize objects. You can reduce that by using server side state saving but than you need more server memory and reduce clustering performance. However, as Norman said, we do not see "performance" as a big issue for JSF at all. It performs "good enough" for the vast majority of web applications. Having said that, I'd love to see Seam integrated with other web frameworks because not everyone is sold on JSF. But given the resources we have, this type of integration will probably need to come from the community ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072627#4072627 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4072627 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
