Its like the guys who thought up the spec, never actually built something in anger before it was all approved and released and that sort of thing. It is just hard to do stuff in it that is really quite simple using normal Servlet style stuff. I.e. links to other portlets. The generated url is different on a per portal basis... so you can't hardcode it if you want to be portable... and each portal vendor seems to provide their own odd way of doing things. Argh.
And Portlets.... I spent the best part of last week trying to find a Wiki Portlet for JBoss Portal. A tricky task.
The only one that seemed to work is JBoss' own version and even then it doesn't seem to render the styles in the right place. We tried to get Xwiki working on JBoss and got so far with this list of changes:
- changed XWikiPortletRequest to enable a conversion to a HttpServletRequest
- modified components.xml to wire up core portlet components properly
- change to stylesheets2.vm for IE directive
- change to XWikiPortletResponse to enable conversion to a HttpServletResponse
- added jboss-portlet.xml
- added jboss-web.xml
- changed the authorization to use container based stuff
It still didn't work. And when code was changed to make certain areas of the screen render, it was all over the show. Never mind the fact that it wasn't consistent in what it rendered and when.
Ah well. Its not that Xwiki isn't good... it looks great. The portlet support just isn't there at all yet.
Lets go back to Liferay....

