Issue #438 has been updated by Clément OUDOT.
Seems the buggy code is in PullableJndiService.java:
<pre>
//
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// VADE RETRO : Directory may store dates in GMT or
local timezone
// Therefore, filters must be adapted to fit this
feature.
// Must find a way to implement this correctly !
// Maybe through a JavaScript expression ?
gc.add(GregorianCalendar.HOUR, -1);
//
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
</pre>
In France/Europe, we have to use -1 or -2 depending on sunlight time saving.
----------------------------------------
Bug #438: asyncFilter does not search on the correct date
http://tools.lsc-project.org/issues/438
Author: Clément OUDOT
Status: Assigned
Priority: Normal
Assigned to: Sébastien Bahloul
Category: Core
Target version: 2.1
Problem in version: 2.0rc2
I tested asyncFilter in a source LDAP service, but the searched date in the
generated filter is not good.
My configuration:
<pre>
<filterAsync>modifytimestamp>={0}</filterAsync>
</pre>
The resulting search request:
<pre>
4f8d79f6 conn=1000 op=64 SRCH base="ou=people,ou=XXX" scope=2 deref=0
filter="(modifyTimestamp>=20120417151052Z)"
</pre>
The searched hour is 15:10, but the real UTC time was 14:10, and my local time
16:10. So a time conversion has been done by adding (or deleting) one hour, but
the correct time difference is 2 hours.
--
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
