Issue in using cqinclude through infinity.json path in granite UI | Community
Skip to main content
C
cq_5_5
October 16, 2015
Solved

Issue in using cqinclude through infinity.json path in granite UI

  • October 16, 2015
  • 1 reply
  • 1362 views

We have the below structure in classic UI:

comp1:  xtype: cqinclude

         path: /apps/thf/components/........./comp2/dialog/items/items/tab1.infinity.json

 

comp2:

          xtype: panel

 

Finding problem in converting it to respective touch ui dialog. 

Any suggestions?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

The cqinclude xtype has been ported in Touch UI , see the "include" component at [1].

See an example at /libs/wcm/core/content/sites/jcr:content/body/account
Property "path" is essential, the "resourceType" property is optional but allow to force the RT for the included path .

Alternatively if you are trying to use in list with the legacy structure, Make use of "datasource" property to generate the list dynamically from the old node structure.

Take exemple on how it's done on the foundation page properties dialog : /libs/foundation/components/page/cq:dialog/content/items/columns/items/tabs/items/advanced/items/section1/items/language/datasource .

The language list is generated by the /libs/cq/gui/components/common/datasources/languages/languages.jsp .

You can do something similar .

 

[1] http://docs.adobe.com/docs/en/aem/6-0/develop/ref/granite-ui/api/jcr_root/libs/granite/ui/components/foundation/include/index.html

1 reply

Sham_HC
Sham_HCAccepted solution
October 16, 2015

The cqinclude xtype has been ported in Touch UI , see the "include" component at [1].

See an example at /libs/wcm/core/content/sites/jcr:content/body/account
Property "path" is essential, the "resourceType" property is optional but allow to force the RT for the included path .

Alternatively if you are trying to use in list with the legacy structure, Make use of "datasource" property to generate the list dynamically from the old node structure.

Take exemple on how it's done on the foundation page properties dialog : /libs/foundation/components/page/cq:dialog/content/items/columns/items/tabs/items/advanced/items/section1/items/language/datasource .

The language list is generated by the /libs/cq/gui/components/common/datasources/languages/languages.jsp .

You can do something similar .

 

[1] http://docs.adobe.com/docs/en/aem/6-0/develop/ref/granite-ui/api/jcr_root/libs/granite/ui/components/foundation/include/index.html

Terms & ConditionsAccessibility statement

Loading footer...