After a little more research, we discovered one more way to get around this
issue. There is a setting in JetspeedResource.properties file,
services.PsmlManager.cacheSize. It is default to 100, meaning maximum 100
psml pages will be cached. We change that to 0 and it fixed this psml
reference
I'd think bypassing the cache would be a bad thing in the future. You
might want to look at the 'refresh' method on the PSMLManager service
interface:
Subject: RE: Refreshing a psml reference
I'd think bypassing the cache would be a bad thing in the future. You
might want to look at the 'refresh' method on the PSMLManager service
interface:
http://portals.apache.org/jetspeed-1/apidocs/org/apache/jetspeed/services/ps
mlmanager
