Earlier today I released the Simple RSS portlet for uPortal. Chuck Severance posted a comment inquiring if it works in Sakai as well, since Sakai has JSR-168 support, just like uPortal.
So I dropped the WAR in and watched the logs with anticipation… success!
2011-03-04 23:15:24,276 INFO main org.apache.catalina.startup.HostConfig - Deploying web application archive simple-rss-portlet-1.0.1.war
2011-03-04 23:15:24,476 INFO main org.sakaiproject.portal.service.PortletTool - Portlet auto-registered with Sakai toolId=portlet./simple-rss-portlet-1.0.1.simple-rss-portlet
2011-03-04 23:15:24,476 INFO main org.apache.pluto.core.PortletContextManager - Portlet Context '/simple-rss-portlet-1.0.1' registered.
2011-03-04 23:15:24,477 INFO main org.apache.pluto.core.PortletContextManager - Registered portlet application with application id '/simple-rss-portlet-1.0.1'
2011-03-04 23:15:24,477 INFO main org.apache.pluto.core.PortletContextManager - Registering 1 portlets for context /simple-rss-portlet-1.0.1
I added the portlet to a site but in place of the main view I received an interesting stacktrace:
Caused by: java.lang.NoClassDefFoundError: javax/el/ValueExpression
This is fairly obvious. uPortal requires Tomcat 6 and hence jstl-1.2. Sakai requires Tomcat 5.5 and hence jstl-1.1. The portlet deploys jstl-1.2. Downgrading the version of JSTL that the portlet deploys to v1.1.2 and redeploying worked a treat:
I’ve updated the install instructions too.
Bring on Tomcat 6 support in Sakai!