Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.2.0.GA
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: Samples
-
Labels:None
-
Environment:ICEfaces EE 4.2 trunk r51707, WAS 9.0.0.2, all browsers
-
Assignee Priority:P2
Description
Each time pressing submit increases the return value for the time by one hour. Not an issue with WAS 8.5.5.9. No server or console errors seen.
To reproduce:
1.) Deploy showcase on WAS 9.0.0.2, Navigate to ace:dateTimeEntry > Time Entry demo.
2.) Select the Time Only radio button
3.) Press the Submit button a few times. Notice that the time above the hour slider does not change but the hour in the 'Selected Date and Time' return value is increased by one for each submit
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The commit(s) made for this issue have caused a regression.
dateTimeEntry > Time Entry demo - When using the 'Date Only' calendar the date selected is returned as one day later. Example selecting July 1 gives a return value of July 2.
This issue was not present in ICEfaces EE-4.2.0 Jenkins build 1 but exists in build 2 and the current EE-4.2.0 code base. Can be seen on Tomcat server.
r51766: added a TimeZone object in the value change event operations in order to perform correct date calculations
The demo should now work as expected on all servers. I tested this on Tomcat 7 and 8, as there were some differences before in the dates being displayed. Now they both work in the same way.
Verified ICEfaces EE-4.2.0 r51766, Tomcat 8, WAS 9.0.0.2, MS Edge, IE 11, 10, 9, 8, FF 47, Chrome 59.
Closing as Won't Fix.
This is not an issue with our component or our framework. The issue is not present if the valueChangeListener is removed from the component in this demo. The valueChangeListener method in the bean of this demo performs some date conversion operations. Basically, it preserves the date parameters (year, month, day) in the time-only mode, and it preserves the time parameters (hour, minute, second) in the date-only mode. This is done by updating the new value (Date object). If these operations aren't performed, the hour doesn't increase by one when clicking on the submit button repeatedly (but the date parameters aren't preserved when moving from the time-only mode to the other modes). So, it's an issue with the platform. The request parameters are all correct. It's an issue with the platform when doing Date operations. It's not clear why it happens, but it has nothing to do with the component or our framework. I committed two different ways to perform these operations in a clean and correct way (previously, the method was using a deprecated API for the Date operations), but the issue is still occurring.