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 Cache

siddin

if we push an XSL change to livesite environment, does it need a Tomcat restart to pick up the changes?

TS 6.7.2 SP1, RHEL 5.2

Find more posts tagged with

Comments

AlexC

The XSl change, do you mean that you have changed XSL component, if so then the deployment will handle invalidating the cache. If this is XSL included by a component or a configuration XSL (page layout, spring config, etc) then it will probably require a restart.

siddin

Sorry i was not very clear about the requirement, this is for a xsl included in the component [html][/html]

AlexC

Included XSL resources have always been a little odd because of the way they are resolved by Xalan/Xerces, we have seen cases where the old XSL was being held on to by the resolver and there is no API to reset it, so often you may have to restart Tomcat.

Test.pdf

Test.rptdesign

ReportViewer1.jpg

ReportViewer2.jpg