AEM Client Libraries folder in /content/dam

Avatar

Avatar

arjun07180302

Avatar

arjun07180302

arjun07180302

11-10-2017

Hi Team,

Got a quick question with respect to the way client libraries work in AEM. Can we have client library folders(cq:clientLibraryFolder) created under /content/dam and there by load static files(.css and .js in DAM) using css.txt and js.txt which are located in same folder(under dam). I know it works all fine when we have under in /apps, /etc and /libs. I am wondering if it works for custom paths as well.

Because, in felix console (under OSGI configMgr), we have an option to configure the 'Allowed Library Paths' for client libraries (Adobe Granite Client Library Manager). But when i configure /content and/or /content/dam, I dont see the client libraries loading in my cq:Page. So, can we have CQ client libraries folders in /content or /content/dam?

View Entire Topic

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

996

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

996

Correct Reply

1.0K
Jörg_Hoh
Employee

11-10-2017

If you allow your "business" to update Javascript libraries and such, it's no longer "business". In that case you are also bypassing all rules of good development, mainly:

  • testing: Has this code been tested?
  • version control: Can you recreate the code which you deliver through your website?
  • traceability: Do you know which code you currently deliver? Or which code you delivered 2 weeks ago?

As Ratna recommended: Don't do it. When you go down that road, it's a clear sign of a broken development process, and you hope to fix it by just bringing new/"fixed" code to production, bypassing any lower environment.

Jörg