Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0020751 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] A. Platform | minor | N/A | 2012-06-13 16:16 | 2012-06-18 16:45 | |||
Reporter | AugustoMauch | View Status | public | |||||
Assigned To | AugustoMauch | |||||||
Priority | immediate | Resolution | fixed | Fixed in Version | 3.0MP13 | |||
Status | closed | Fix in branch | pi | Fixed in SCM revision | 976c8398def2 | |||
Projection | none | ETA | none | Target Version | 3.0MP13 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Review Assigned To | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0020751: API change: time fields are sent in UTC | |||||||
Description | The changeset https://code.openbravo.com/erp/devel/pi/rev/976c8398def2e80de470ab55db222555d88566d8, [^] which fixes issue 20684, has modified the way time fields are sent from the server to the client and vice versa. To be able to support time fields with differente time zones, they have to be sent in UTC, and converted to local time upon being received. This fields used to be sent using the local time of the sender. | |||||||
Steps To Reproduce | There may be clients that are receiving time fields from the server, and expect them to be in the server's local time. Now they will receive UTC times, and are expected to send UTC times too. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0049853) iciordia (manager) 2012-06-15 13:28 |
Approved. Ismael |
(0049855) AugustoMauch (administrator) 2012-06-15 13:33 |
Risk assessment: This change may only affect negatively those who receive a time from the server and parse it to a date with a non-standard function. In that case, the problem will be solved if the non-standard function is changed to support the lack of GMT offset. |
Issue History | |||
Date Modified | Username | Field | Change |
2012-06-13 16:16 | AugustoMauch | New Issue | |
2012-06-13 16:16 | AugustoMauch | Assigned To | => AugustoMauch |
2012-06-13 16:16 | AugustoMauch | Modules | => Core |
2012-06-13 16:17 | AugustoMauch | Relationship added | related to 0020684 |
2012-06-13 16:18 | AugustoMauch | Assigned To | AugustoMauch => iciordia |
2012-06-15 13:28 | iciordia | Note Added: 0049853 | |
2012-06-15 13:28 | iciordia | Assigned To | iciordia => AugustoMauch |
2012-06-15 13:33 | AugustoMauch | Note Added: 0049855 | |
2012-06-18 16:41 | AugustoMauch | Status | new => scheduled |
2012-06-18 16:41 | AugustoMauch | fix_in_branch | => pi |
2012-06-18 16:45 | AugustoMauch | Status | scheduled => resolved |
2012-06-18 16:45 | AugustoMauch | Fixed in Version | => 3.0MP13 |
2012-06-18 16:45 | AugustoMauch | Fixed in SCM revision | => https://code.openbravo.com/erp/devel/pi/rev/976c8398def2e80de470ab55db222555d88566d8 [^] |
2012-06-18 16:45 | AugustoMauch | Resolution | open => fixed |
2012-06-18 16:45 | AugustoMauch | Status | resolved => closed |
Copyright © 2000 - 2009 MantisBT Group |