Three new portlet releases

I am pleased to announce three new portlet releases.

Basic LTI Portlet – 1.4.2 (source, maven)

Sakai Connector Portlet – 1.5.2 (source, maven)

Simple RSS Portlet – 1.2.2 (source, maven)

All portlets are available as source tags or as artifacts in Maven central.

These releases ensure uPortal 4 compatibility, fixes a few bugs and adds seven new languages, including German (de), Spanish (es), French (fr), Japanese (ja), Dutch (nl), Portuguese (pt) and Swedish (sv).

Most of these languages were made possible by auto-i18n, an automated translation tool I developed. For native speakers, I am very interested to receive your feedback on the quality of these automatically translated languages. You can enable the various languages using the User Locale Selector portlet in uPortal.

Both the Basic LTI Portlet and Sakai Connector Portlet are now finalised and very soon should appear in the main uPortal release, as they have (almost) graduated from the Jasig incubation process!

Update: New release versions for each portlet (updated above) – slight restructuring ready for the uPortal portlet overlay.


External Calendaring Service for Sakai

Over the past few months I’ve been working on and off on a project to make working with iCal files within Sakai really easy – I call it the External Calendaring Service. I am pleased to announce that this is now available for your delicious consumption.

It leverages iCal4J and allows you to turn Sakai CalendarEvents into iCal files. You can aggregate a number of events together to create one calendar and then attach it to an email, then update events, delete events, add and remove participants etc. This is really useful when tools want to send out notices about events, so an obvious integration for this is the Signup tool, which fully integrates with the service.

Check out the Javadocs for the complete info:

The service is available in source code via the Sakai SVN repo, but to integrate with your project just add the following dependency to your POM and you are done:



Feedback or suggestions for features warmly welcomed.

Reduce your Sakai CLE startup time

There is a current discussion on the sakai-dev list about the recent switch to Tomcat 7 and some new features in Tomcat that meant startup times took a bit longer than they used to.

As it turns out there is a new feature in Tomcat 7 that scans jar files for various Servlet 3 features. However the CLE code doesn’t use any Servlet 3 features yet.

So we can just disable the scanning and cut our startup times by a fair amount.  On my local full trunk deployment I was able to reduce my startup from 175 seconds down to 89 seconds.

To do this, in, set:


So far, all CLE tools in 2.10 appear fully functional. If you try this and experience issues, please let me know in the comments, or post on list.