...moving thread from user list...
David,
This content-server/page aggregation issue remains with the latest CVS HEAD version. The problem in a nutshell is that the SESSION_CONTENT_PATH_ATTR value used by the SimpleContentLocator appears to be set once per session by the PageAggregator and contains only the layout decoration paths for the page. Custom portlet decoration paths do not make it into the path. This issue is apparently related to JiRa "JS2-24".
Instead of updating the paths in the Perhaps the decorator.vm should include its name in the image urls so that the more general default search paths would come into play, (this is already done within the layout css stylesheets). For example, "/content/images/maximize.gif" could be modified to be "/content/my_portlet_decorator_name/images/maximize.gif" at a minimum. If done, the hard coded "portlet/html/jetspeed" path could be removed. Specifying a more unique path, (i.e. with the decorator name in it), would seem to be better than asking the page aggregator and content-server to dynamically manage content search paths as portlets are rendered. Relying on paths also can lead to confusion in the likely event that image file names are the same! Thoughts?
Randy Watler
Randy Watler wrote:
Scott/All,
I have successfully added new portlet and layout html decoration directories to jetspeed and so far so good. However, the content for the portlet action icons, (maximize, minimize, etc...), keeps being served from the "jetspeed" decoration images directories. I enabled debug output for the content-server and verified that it is indeed serving the "jetspeed content". With a little digging, it appears that these defaults are comming from the jetspeed-spring.xml configuration for the PageAggregatorImpl. Unfortunately, I am not sure what should be modified and where.
As you know, the decorator.vm template uses the current action list urls to generate the html fragments. These look like "/content/images/*.gif. Apparently, the PageAggregatorImpl looks only here for the images:
layout/html/<my layout decoration name> portlet/html/jetspeed portlet/html layout/html generic/html html
Consequently, it ends up finding the images in the jetspeed decoration directory instead of in portal/html/<my portlet decoration name> where I would expect it to be looking!
It appears that the same thing is happening in the sample default-page.psml HW_App::PreferencePortlet that attempts to use the "metal" portlet decorations... the action icons are actually the ones from the "jetspeed" decorations.
It appears to me that there is only one workaround: add the new portlet decorations to the jetspeed-spring.xml. Am I on the right track here? BTW, I am working with CVS HEAD as of 8/21 AM.
Please let me know if there is a fix, a better workaround, or if I can help fix this in any way.
Randy Watler
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
