Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.2.BETA
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces 4 trunk r50154, Tomcat 8, all browsers
-
Assignee Priority:P2
Description
The following events fail to trigger an ajax report in the QA Calendar ajax test app:
"dateSelect" Event Test (Default render/execute)
"dateSelect" Event Test (execute=@all render=@all)
Default Event Test (execute=@all render=@all)
"dateSelect" Event Test w/ ValueChangeListener attribute (Default execute/render)
These tests passed using 4.1.1, libs, but not 4.2 Beta. The test is last known to have passed in automation Dec 12, 2016.
Test app /calendarAjax.jsf can be found at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/dateTimeEntry
"dateSelect" Event Test (Default render/execute)
"dateSelect" Event Test (execute=@all render=@all)
Default Event Test (execute=@all render=@all)
"dateSelect" Event Test w/ ValueChangeListener attribute (Default execute/render)
These tests passed using 4.1.1, libs, but not 4.2 Beta. The test is last known to have passed in automation Dec 12, 2016.
Test app /calendarAjax.jsf can be found at:
http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/dateTimeEntry
Issue Links
- depends on
-
ICE-11225
Implement multiple client behaviour handling in ACE components
-
- Resolved
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
All ACE components should be modified so that they can handle multiple client behaviours associated with a single client event.
Show
Mircea Toma
added a comment - All ACE components should be modified so that they can handle multiple client behaviours associated with a single client event.
Provide the client ID of the component as the javax.faces.source when 'dateSelect' behavior event is triggered.
Show
Mircea Toma
added a comment - Provide the client ID of the component as the javax.faces.source when 'dateSelect' behavior event is triggered.
Verified ICEfaces 4 trunk r51435. Tomcat 8, IE 11, FF 47, Chrome 57.
Show
Liana Munroe
added a comment - Verified ICEfaces 4 trunk r51435. Tomcat 8, IE 11, FF 47, Chrome 57.
The issue is triggered whenever the ace:dateTimeEntry component has two or more client behaviours attached. On the client side the component is not able to interpret the list of behaviours attached to a certain event, it assumes that there is only an ace:ajax client behaviour. This causes the client side code to fail once the ace:animation behaviour is added.