Thanks to a lot of work by Ian Boston and David DeWolf we have support for JSR-168 in Sakai.
I just finished fiddling around with it and wrote some documentation. Here are my notes about it...
I still need to work more on this documentation and play more with developing portlets- but the basic support seems solid and there.
I recently finished some improvement of the auto registration process for Sakai support of JSR-168 portlets.
I also wrote some documentation which is in
/reference/docs/architecture/sakai-168-portlets.doc
And attached.
The primary feature is to add more control to the portlet registration process
including the ability to add a tool registration file for a portlet without modifying the
portlet war file as well as a property to control the auto-regitration behavior.
Requires modifications to tool/ActiveTool up to revision 21132.
See requirements SAK-8022 and SAK-8349.
This puts JSR-168 support in Sakai 2.4 in a really solid state.
My next steps are actually to adapt refactor my existing portlets a bit write some simple sample portlets to complete my documentation on how to write a portlet in Sakai.
If you want to use this code, you need to take the follwoing steps:
- Get maven 2 working
- Check out the trunk of Sakai
- Check out the charon_velocity branch
- Make the following changes to the root pom.xml - comment out osp and replace portal with charon_velocity portal
-
+
-
+
- Compile it all - perhaps check to see if it starts
- Add a war file with Pluto 1.1 portlets in it to your webapps directory (I have one attached)
- Start Tomcat - look at the logs as per the documentation - make a site, add some portlets
- If you are adventurous check this out
https://source.sakaiproject.org/svn/portlet/trunk/
and put in a director called portlet - you compile this with "maven bld dpl" as it is not yet M2.
Lather, rinse, and repeat.
My work was small and simple clean up - Ian and David did the very heavy lifting on this effort.