[JBoss JIRA] Created: (RF-3080) a4j:actionparam is not working properly in RichFaces 3.2
by Linh Le (JIRA)
a4j:actionparam is not working properly in RichFaces 3.2
--------------------------------------------------------
Key: RF-3080
URL: http://jira.jboss.com/jira/browse/RF-3080
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: JBoss app server 4.3, JSF 1.2, Richfaces 3.2
Reporter: Linh Le
Does the fix for this issue "http://jira.jboss.com/jira/browse/RF-2634" really get included in RichFaces 3.2 release???
I have just upgraded from Richfaces 3.1.4 to 3.2, and the assignTo of a4j:actionparam does not work properly anymore. I worked fine with 3.1.4. Why???
Specifically, I'm having a4j:actionparam inside an a4j:support onclick event. Then the a4j:support is put inside a h:panelGrid. At the very first click on the panelGrid, the bean property is NULL. The value was not set to the bean property of the assignTo attrib at all, but it is set after the action listener method completed its execution. The bean property should be set before the action listener method get executed (like in 3.1.4). Therefore, for any subsequent click on the panelGrid, the bean property shows the value of the previous click.
Your prompt response is highly appreciated.
--
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
14 years, 3 months
[JBoss JIRA] Created: (RF-4471) Usage of ImageIO in ResourceBuilderImpl causes memory leak
by Philipp Schoepf (JIRA)
Usage of ImageIO in ResourceBuilderImpl causes memory leak
----------------------------------------------------------
Key: RF-4471
URL: https://jira.jboss.org/jira/browse/RF-4471
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.6
Environment: any
Reporter: Philipp Schoepf
It seems as we found a memleak in the ResourceBuilderImpl class. The call to
ImageIO.setCache(false)
causes sun.awt.AppContext to statically initialize itself (inside static initialization of IIORegistry). The problem is that AppContext seems to hold a static reference to the contextclassloader of the calling thread. When our application gets undeployed the reference to the applications classloader is still hold by AppContext causing that loaded classes cannot be garbage collected.
I only checked richfaces 3.16 but if ResourceBuilderImpl still exists in 3.2 stream I suppose that the problem exists there as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (RF-3967) tabPanel: incorrect handlers in test-application: ondownclick, onupclick, onorderchanged, ontopclick, onbottomclick, onheaderclick
by Tsikhon Kuprevich (JIRA)
tabPanel: incorrect handlers in test-application: ondownclick, onupclick, onorderchanged, ontopclick, onbottomclick, onheaderclick
----------------------------------------------------------------------------------------------------------------------------------
Key: RF-3967
URL: https://jira.jboss.org/jira/browse/RF-3967
Project: RichFaces
Issue Type: Sub-task
Affects Versions: 3.2.2
Reporter: Tsikhon Kuprevich
Assignee: Tsikhon Kuprevich
Fix For: 3.2.2
need to research where are they getting from
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months