[ http://jira.jboss.com/jira/browse/JBSEAM-3024?page=all ] Alex Savitsky updated JBSEAM-3024: ---------------------------------- Attachment: Perf.zip Eclipse WST project in Maven format. Either import it into Eclipse (requires Maven 2 eclipse plugin), or build WAR using Maven. After deploying, access the home page, and observe the page load times for first and subsequent accesses. My average was about 1.3-1.5 seconds (FasterFox page load timers are useful here). Now, update Seam version in POM from 2.0.2.GA to 2.0.1.GA, and repeat the above steps. The observed average load times will be much lower (0.3-0.4 seconds in my case). Keep in mind, this is a very simplified version of the actual application I had first observed this issue with. I've tried to preserve the general architecture used, but scaled back on # of controls and DB entities. The actual app executes queries on a four-level deep entity hierarchy, and also uses Tomahawk sortable headers, resulting in load times of about 30 seconds for 2.0.2 (as opposed to about 3 seconds on 2.0.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3024?page=all ] Jay Balunas reassigned JBSEAM-3024: ----------------------------------- Assignee: Shane Bryzak -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3024?page=comments#action_12414135 ] Shane Bryzak commented on JBSEAM-3024: -------------------------------------- Which container should your test case be deployed to? I tried both JBossAS 4.2.2 and Tomcat 5.5 and neither worked - actually, under Tomcat it deployed with errors, however then threw the following exception when accessing the home page: SEVERE: Error Rendering View[/index.xhtml] javax.el.PropertyNotFoundException: /index.xhtml @15,55 value="#{testService.displayType}": Target Unreachable, identifier 'testService' resolved to null at com.sun.facelets.el.TagValueExpression.getType(TagValueExpression.java:62) at org.jboss.seam.ui.component.UIEnumItem.getValue(UIEnumItem.java:49) at com.sun.faces.renderkit.RenderKitUtils.getSelectItems(RenderKitUtils.java:285) at com.sun.faces.renderkit.html_basic.MenuRenderer.renderSelect(MenuRenderer.java:776) at com.sun.faces.renderkit.html_basic.MenuRenderer.encodeEnd(MenuRenderer.java:279) at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:850) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3024?page=all ] Shane Bryzak closed JBSEAM-3024. -------------------------------- Resolution: Done Closing this issue, as Seam.getEjbDescriptor() seemed to be the cause. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-3024?page=all ] Pete Muir closed JBSEAM-3024. ----------------------------- Resolution: Duplicate Issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira