[Building Sakai] heads-up on 2.9.x upgrade: see jldap provider bug fixes at SAK-23689 and SAK-23719

[Sam Ottenhoff]

Thanks Bill for the excellent JIRAs and patches.

Both of the patches are now in trunk and are awaiting verification before
they are merged into 2.9.x.

These are both difficult to reproduce, but others who have a local LDAP
connection should be able to test and verify.  The caching issue can
probably be replicated fairly easily by setting the UserDirectoryService
callCache to a very low value to get values out of the JLDAP cache.

As a next step, I'd like to see us remove the JLDAP cache completely in
trunk Sakai.  The UserDirectory cache holds all relevant user information
making the JLDAP cache redundant and confusing.

Thanks,
Sam


On Tue, Jun 18, 2013 at 3:36 PM, Niebel, William (wdn5e) <
wdn5e at eservices.virginia.edu> wrote:

>   For the jldap bug fix, see:  SAK-23689 JLDAP fails on ldap data cached
> and unexpired
>     For how this manifested for us, see SAK-23691:  Immediate receipt
> option broken for mailarchive sender who is JLDAP-provided
>
> For the jldap bug fix, see:  SAK-23719 JLDAP fails if final iteration user
> is blacklisted in method getUsers()
>     For how this manifested for us, see SAK-23720:  Site Info sometimes
> omits some user names for participant list of some sites
>
> Bill Niebel
> University of Virginia
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130618/94bd9d2b/attachment.html