[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2704) Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors
by Siarhei Dudzin (JIRA)
Performance during iteration (datatable, repeat) in the UI with value bindings that run through interceptors
------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2704
URL: http://jira.jboss.com/jira/browse/JBSEAM-2704
Project: JBoss Seam
Issue Type: Bug
Components: Performance and Scalability
Affects Versions: 2.0.1.GA, 2.0.0.GA
Environment: Seam 2.0.0, 2.0.1
Reporter: Siarhei Dudzin
"Since we don't cache this, a particular backing bean might be called hundreds or thousands of times during rendering of a datatable, if a value binding has to be evaluated for each row. If the backing bean is a Seam component, injection of dependencies will occur for every call, involving potentially thousands of map lookups."
There is a discussion thread with a bit more data: http://www.seamframework.org/Community/SeamPerformanceOptimization
The issue is also recognized at the seamframework.org site itself: http://www.seamframework.org/Documentation/TuningTheSeamWebsite#H-Iterati...
Since the issue it known, this JIRA report is created for better traceability.
--
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
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2562) 'Transaction failed' JSF message when number of restriction in EntityQuery changes
by Siarhei Dudzin (JIRA)
'Transaction failed' JSF message when number of restriction in EntityQuery changes
----------------------------------------------------------------------------------
Key: JBSEAM-2562
URL: http://jira.jboss.com/jira/browse/JBSEAM-2562
Project: JBoss Seam
Issue Type: Bug
Components: Framework
Affects Versions: 2.0.1.GA
Environment: JBoss AS 4.2.2, Windows XP
Reporter: Siarhei Dudzin
When getRestrictions() from EntityQuerry returns dynamic list with restrictions a JSF error message 'Transaction failed' is shown (no exceptions just a message). I noticed this happens when the size of the list is decreased in comparison with the previous request (There is also a warning in the logs).
While this JSF message is shown the query still works!
After some debugging I've found that the underlying error is that a value binding could not be found. A temprorarily workaround is to keep the restriction list constant by filling the 'gaps' with placeholders like #{true}=true (just to keep the size constant).
--
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
15 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2881) Conversation Switcher doesn't work with natural conversations
by Caleb Land (JIRA)
Conversation Switcher doesn't work with natural conversations
-------------------------------------------------------------
Key: JBSEAM-2881
URL: http://jira.jboss.com/jira/browse/JBSEAM-2881
Project: Seam
Issue Type: Bug
Components: JSF Controls, JSF Integration
Affects Versions: 2.0.2.CR1
Environment: Seam 2.0.2.CR1, Mac OS X 10.5, Java 1.5.0_13
Reporter: Caleb Land
The Switcher component's (org.jboss.seam.faces.Switcher) switch() method does not work correctly when using natural conversations.
The issue is related to line 102 (in trunk and in 2.0.2.CR1) where seam tests whether the selected item is an outcome or a conversation id:
boolean isOutcome = conversationIdOrOutcome==null || !Character.isDigit( conversationIdOrOutcome.charAt(0) );
The problem is that with natural conversations, the value of conversationIdOrOutcome is something like "accountEdit:4" so the switcher thinks it's a view.
I copied the code from the Switcher and created a new component and replaced that line with:
boolean isOutcome = conversationIdOrOutcome==null ||
(!Character.isDigit(conversationIdOrOutcome.charAt(0)) && conversationIdOrOutcome.indexOf(':') < 0);
and it works correctly. Of course this approach is naive, but it seems to work for me.
--
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
15 years, 8 months