Issue #626 has been updated by Clément OUDOT.

Status changed from Rejected to Assigned
Assigned to set to Raphaël Ouazana
Priority changed from Normal to Low
Target version set to 2.0.4

Hi,

sorry to reopen, but I still think there is a problem.

Java int max value is 2147483647, which in UNIX time is equal to Tue, 19 Jan 
2038 03:14:07 GMT. So if we have a UNIX timestamp after this value (for example 
to manage an expiration date in 2099), we cannot convert it.

We should propose another method signature that accept Long value.
----------------------------------------
Bug #626: Interger limitation in unixTimestampToADTime
http://tools.lsc-project.org/issues/626

Author: Clément OUDOT
Status: Assigned
Priority: Low
Assigned to: Raphaël Ouazana
Category: Core
Target version: 2.0.4
Problem in version: 


I try to use unixTimestampToADTime but the method expect an Integer (or a 
String that will be converted into Integer).

Java has a limitation on Interger range: 
http://www.cafeaulait.org/course/week2/02.html

So I got those errors:
<pre>
org.lsc.utils.JScriptEvaluator - oct. 21 16:44:45 - ERROR - 
javax.script.ScriptException: sun.org.mozilla.javascript.EvaluatorException: 
Impossible de convertir 185542587100800 en java.lang.Integer (<Unknown 
source>#10) in <Unknown source> at line number 10
</pre>

We should use long to be able to parse big timestamps.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev

Reply via email to