Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces
-
Assignee Priority:P1
Description
Server side onElementUpdate implementation notifies on element addition instead of sending the notification on element replace or remove.
Here are Marks' findings:
"I updated my code and ran the memoryLeak test application with server side update notification, watching the Firebug Net tab, and what I saw was that when the ace:dateTimeEntry components are added to the page, the notification is sent:
<eval><![CDATA[ice.notifyOnElementUpdateCallbacks(['frm:j_idt7:0:testDateOne', ...
But when the ace:dateTimeEntry components are removed from the page, the notification is not sent. This is exactly reversed. We don't want their notification when they're added, only when they're removed."
Here are Marks' findings:
"I updated my code and ran the memoryLeak test application with server side update notification, watching the Firebug Net tab, and what I saw was that when the ace:dateTimeEntry components are added to the page, the notification is sent:
<eval><![CDATA[ice.notifyOnElementUpdateCallbacks(['frm:j_idt7:0:testDateOne', ...
But when the ace:dateTimeEntry components are removed from the page, the notification is not sent. This is exactly reversed. We don't want their notification when they're added, only when they're removed."
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #35676 | Fri May 31 11:03:20 MDT 2013 | mircea.toma | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/impl/context/DOMPartialViewContext.java
|