nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Livesite Runtime - JAR & XSLT Caching

k1DBLITZ

It appears the livesite runtime service (windows) caches jars and xslts on startup.

We've had to restart the livesite service for changes to appear immediately.. but we noticed that a change to an xslt that was deployed eventually showed up.

Does anyone know what the cache time limit is or how to configure that time?

Thanks.

Find more posts tagged with

Comments

AlexC

What version of livesite?

We do not explicitly cache any jars, that is the function of the classloader and you should refer to your container/JRE flags if you want non-default behavior. XSLT stylesheets do get cached (LS 6.7.2 SP2 is when I think it was added). The cache is cleared when you deploy any page, so you can do "Invalidate Runtime" on any page and it should clear the XSLT cache. There is one catch, if you use XSL include, the included file may get cached by Xalan-J internally (we have heard of this in the wild but have not seen an actual reproduceable case, if you have such a case please contact support).

k1DBLITZ

I believe it is 7.1? That is the version of the installer that was used.

AlexC

Post 7.0, XSLT stylesheet is also cached but any deployment should clear it. Have you tried deloying a page and seeing if XSLT is correctly refreshed?