updateDelay not forcing recompile of modified FTLs

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

tarh33l

Hi everyone,
      I'm developing some FTLs in Share and finally got fed up with having to bounce the webapp for each change I made. I started digging into this and found the following lines in "custom-slingshot-application-context.xml":

   <bean id="webframework.webscripts.templateprocessor.freemarker" class="org.springframework.extensions.webscripts.processor.FTLTemplateProcessor">
      <property name="searchPath" ref="webframework.webscripts.searchpath" />
      <property name="defaultEncoding"><value>UTF-8</value></property>
      <property name="updateDelay"><value>1</value></property>      
      <property name="templateProcessorRegistry" ref="webframework.webscripts.registry.templateprocessor" />
   </bean>

   <bean id="webframework.templates.templateprocessor.freemarker" class="org.springframework.extensions.webscripts.processor.FTLTemplateProcessor">
      <property name="searchPath" ref="webframework.templates.searchpath" />
      <property name="defaultEncoding"><value>UTF-8</value></property>
      <property name="updateDelay"><value>1</value></property>
      <property name="templateProcessorRegistry" ref="webframework.templates.registry.templateprocessor" />
   </bean>‍‍‍‍‍‍‍‍‍‍‍‍‍

I've changed "updateDelay" from the default of "0" to "1". This is supposed to tell the template processor to look for modified FTLs every second. Unfortunately, this is not working in Share (3.3.1). Does anyone know why this is the case? If not, is there an alternative way of forcing a refresh on modified FTLs (without a server restart)?

Thanks!
- Terence

mikeh

Add the following config to share-config-custom.xml in the tomcat/shared/classes/alfresco/web-extensions folder.

<alfresco-config>
   <config evaluator="string-compare" condition="WebFramework">
      <web-framework>
         <!– Autowire Runtime Settings –>
         <autowire>
            <!– Pick the mode: development, preview, production –>
            <mode>development</mode>
         </autowire>
      </web-framework>
   </config>
</alfresco-config>‍‍‍‍‍‍‍‍‍‍‍

You don't need to bounce the webapp (although with the share.war deployed in a separate Tomcat server, this should only take 10 seconds or so…) you can reset the webscripts instead at /share/service/index

Finally, you can wrap the reset webscripts POST request in a simple script that calls curl if you like.

Thanks,
Mike