AEM 6.2 Component Specific ClientLibrary

[ankurk67503819]

Hi Team,

While going through the we retail reference site , I noticed for each component they have created separate clienlibaries like below-

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"

jcr:primaryType="cq:ClientLibraryFolder"

categories="[we-retail.components.base,we-retail.components.articles-list]"/>

aem-sample-we-retail/.content.xml at master · Adobe-Marketing-Cloud/aem-sample-we-retail · GitHub

Categories we have we-retail.components.base,we-retail.components.articles-list.

So what is the use of we-retail.components.articles-list. in this case.

Even if we specify only we-retail.components.base it works the same way.

Also what is the benefit of creating a separate client library in each component folder rather we could create them in etc/design/site/css or js files?

[Techaspect_Solu · Accepted solution]

Hi ankur,

The main reason for using Component Specific ClientLibrary is fast accessibility to a component if there are any changes to be done.

User can embed all the individual client libs under /etc/designs/site, So that we can prioritize the order of client libs while loading.

If user creates all the clientlibs at one place and there are some minor changes has to be done, user need to go through all the clientlibs and find out which file has to be modified.

Using Component Specific ClientLibrary is kind of improvement. Moreover both are having same functionalities which are implemented in different way.

Thanks,

Techaspect Solutions.

[ankurk67503819]

Hi,

So apart from fast accessibility there is no benefit is it?

One more question I asked above what is the use of we-retail.components.articles-list. in this case.

Regards