FYI This may be common knowledge, but something I learned last week is
that uPortal and some portlets use an internal app page caching approach
to cache static assets (*.js and *.css) in ehcache using a page caching
filter defined in web.xml, ehcache, and the spring app context:
https://github.com/Jasig/uPortal/blob/uportal-4.1.0-RC2/uportal-war/src/main/webapp/WEB-INF/web.xml#L135
https://github.com/Jasig/uPortal/blob/uportal-4.1.0-RC2/uportal-war/src/main/webapp/WEB-INF/web.xml#L283
https://github.com/Jasig/uPortal/blob/uportal-4.1.0-RC2/uportal-war/src/main/resources/properties/contexts/cacheContext.xml#L77
https://github.com/Jasig/uPortal/blob/uportal-4.1.0-RC2/uportal-war/src/main/resources/properties/ehcache.xml#L419
This static asset page caching behavior can be disabled by clicking the
Disable Aggregation in the admin portlet, or by adding
-Dorg.jasig.resourceserver.utils.aggr.aggregated_theme=false to your
CATALINA_OPTS so you can make changes to js or css files and have them
reflect immediately on page refresh.
Note: Tomcat may also cache static content, which can be turned off on
your dev machine by adding these two parameters to your
$catalina_home/conf/context.xml file:
<Context sessionCookiePath="/">
<Parameter name="cachingAllowed" value="false" />
<Parameter name="antiResourceLocking" value="false" />
This is documented at
https://wiki.jasig.org/display/UPM40/UE+Development+Tips.
--
James Wennmacher - Unicon
480.558.2420
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
