topic Re: Using a folder rule to execute a script from the classpath? in Alfresco Archive

Using a folder rule to execute a script from the classpath?

dnallsopp — Tue, 21 Aug 2012 11:13:26 GMT

I would like to use a folder rule to trigger a script, using the normal "Manage Rules" wizard. The pull down menu for "Execute Script" seem to be populated from the scripts in Data Dictionary/Scripts in the repository - this all works fine.However, is there a way to include scripts from the classpat

Re: Using a folder rule to execute a script from the classpath?

scouil — Tue, 21 Aug 2012 14:35:26 GMT

Hello,

You can of course add the scripts in your file system in
<tomcat home>\shared\classes\alfresco\extension\scripts\yourscript.js

However the scripts in the file system have a major drawback: every time you update a script, you have to fully restart your server.

Re: Using a folder rule to execute a script from the classpath?

dnallsopp — Tue, 21 Aug 2012 16:37:22 GMT

Hi,

I tried adding a script to:

/opt/alfresco-4.0.e/tomcat/shared/classes/alfresco/extension/scripts/

and restarting the server, but no luck - the script doesn't seem to be picked up by the menu in Edit Rule->Perform Action->Execute Script.

Only the "Start Pooled Review and Approve Workflow" script appears in this menu.

I also tried the script in /opt/alfresco-4.0.e/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/extension/scripts/ and restarting, but again no luck - not sure whether this should have the same effect as putting it in shared.

The script is just a one-liner as shown below, though presumably it makes no difference since it won't be read until execution time:

logger.log('+++ Logging test script +++');‍

Re: Using a folder rule to execute a script from the classpath?

scouil — Wed, 22 Aug 2012 07:23:53 GMT

Hello.

Then the extension/scripts folder isn't automatically picked up, my bad.
You probably need to register your action through spring then.

webapps/alfresco/WEB-INF/classes/alfresco/* is mostly the same as shared/classes/alfresco/extension . However, webapps/alfresco/* is from Alfresco jar and will be lost when you upgrade alfresco that's why the good practice is to put your extensions in shared/*

Regards,