Dan McCallum's blog

I received feedback that the following notes on Sakai's LDAP provider behavior would be worthwhile archiving more visibly than on the Sakai dev list, so I'm reprinting them here. See here for the context of the entire thread.

...snip....

So, today I was getting ready to commit a set of changes to the Sakai JLDAPDirectoryProvider. All the unit and integration tests green-bar'd in Eclipse, but I thought it would be a good idea to verify that they also pass when executed from Maven. This way lies madness, as the kids say...

Last night I was wrestling with a Ruby SOAP client of a long-running web-service. After 60 seconds, the script would exit with the following stack:

If you've tried to use Melete 2.2 in a Sakai that's already been deployed in the wild for some time, you may have encountered error screens when accessing a Melete placement on an existing Site.

Sakai Aliases map between logical, human-friendly names and Sakai-internal Entity references.

I've heard complaints from time to time about Sakai's layout management w/r/t large sets of Site enrollments leading to an unmanageable set of top-nav tabs. This is mitigated, to some extent, by the appearance of a select box in the nav bar, to contain references to Sites which would otherwise cause truly unsightly tab overlow. For example: