Testing XSLT in WPC
I'm wondering what methods folks are using when they are testing out XSLT changes. It appears as though one must bounce the portal in order for XSLT changes to take affect.
Is there an easier way to have a change to the XSLT for a document type take affect? I'd prefer to avoid cycling the portal everytime I make a change. The velocity of development is slowing to a halt.
Praveen Kumar Gudapati replied
Check the Editor Service Cache in the below link:
I would set the Default Time-To-live setting to 1, so that the cached content expires after 1 sec.