Aggregated Dependency Outpu - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

If you do enable dependency aggregation then you can expect the following behavior to occur. If the file A.js contains:

var a = 1;

and the file B.js contains:

var c = a + b;

and you have a WebScript template containing the following:

<@scriptsrc="${url.context}/res/A.js"group="calc"/>
   <@inlineScript group="calc">
      var b = 1;
   </@>
<@script src="${url.context}/res/B.js" group="calc">

When the final page is rendered in the source you would see an import like this:

<scripttype="text/javascript"src="/share/res/20146f7250123ea2437a0d16d5c323.js"></script> <!-- Group Name: "calc" -->

The source of that file would contain:

var a = 1;
var b = 1;
var c = a + b;

The resource name is an MD5 checksum generated from the combined source code. The generated resource is cached on the server so that it doesn’t need to be generated each time. If extra content is added to the group (even dynamically by a module) then the resource will be regenerated and the checksum will naturally change to ensure that the browser requests a different file.