[
http://jira.jboss.com/jira/browse/JBSEAM-890?page=comments#action_12353851 ]
Peter Muir commented on JBSEAM-890:
-----------------------------------
I'm actually having problems reproducing this, but I can see how it could happen.
Anyway, I've committed a fix to CVS which should do it. Guy, I need you to test this
for me (btw thanks for all the issues you've been raising :) ).
Ok, so when Seam moves to using the 1.2 RI by default we can look at going with the simple
option as above (and perhaps keep this fix for legacy code)
UISelectItems leaks memory/state
--------------------------------
Key: JBSEAM-890
URL:
http://jira.jboss.com/jira/browse/JBSEAM-890
Project: JBoss Seam
Issue Type: Bug
Components: JSF
Affects Versions: 1.1.6.GA
Reporter: Guy Veraghtert
Assigned To: Peter Muir
Fix For: 1.1.7.GA
When you use UISelectItems with a no selection label, a ConverterChain is set as the
converter of the component. As the converter is part of the component state, upon a
postback that converchain will be restored. However, when addNoSelectionLabel() is called
in UISelectItems (this method is called indirectly when getValue() is called), a new
ConverterChain instance is created and set as the converter of the component, the original
converter of that component (which was already a converterchain) will be added to the new
ConverterChain. As a result, NoSelectionConverter will be added to the chain more than
once, and worse: memory leaks/state grows and grows when multiple postbacks are made to
the same page (as the chain grows and grows).
--
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