atomhttp://forums.alfresco.com/viewtopic.php?t=3502&start=0&postdays=0&postorder=asc&highlight=uportal
Sorry for the late reply, the last two weeks have been pretty hectic. One week in Boston and the next at Heartland college to teach a portlet training class with Cris Holdorph.
However, I had a day to re-examine the alfresco portlet in uPortal and am happy to say that the portlet appears to be 100% functional. Kevin's comments regarding session attributes led me in the right direction. The problem proved to be a configuration issue in tomcat. I didn't know that sharing such data between the PortletSession and another webapp required emptySessionPath to be set to true in tomcat's server.xml connector config.
So, the changes necessary for deploying alfresco's portlet are:
1) modify the portlet.xml file to conform to the JSR 168 spec by adding the expiration-cache element. (uPortal tends to be very picky about this where as many other portal's will ignore it even though the spec requires the tag)
2) remove portlet-api-lib.jar from WEB-INF\lib uPortal often has issues if this jar is present within a portlet.
3) modifying tomcat's server.xml to include emptySessionPath="true" setting within the Connector definition.
NOTE: with these changes in place the standard method for deploying and publishing a portlet to uPortal may be used (portlet definition ID: alfresco.AlfrescoClient).
Thank you for your time and patience in this matter.
_________________
Lennard Fuller
Senior Software Engineer
Unicon Inc
No comments:
Post a Comment