Hi @ArpitVarshney, My core bundle pom.xml has already included * as dependency as below.   <plugin><groupId>org.apache.felix</groupId><artifactId>maven-bundle-plugin</artifactId><extensions>true</extensions><configuration><instructions><!-- Do not inline jars, include as jar files --><Embed-Dependen...

Thank you Briankasingli

Got another solution. Created 6 different single dimensional string arrays which is supported by OSGI. Then added all these 6 string array to a list and then used that list in my logic and that seems to be working.

I think, there is a misunderstanding here. We have a config node in our apps folder for each OSGI configuration right. That is basically a xml file where we define our OSGI properties which is then picked by our component or service. How we can define a 2D array in this osgi config node is my questi...

Thanks Brian for your answer. I understand we have string array representation as below in the osgi xml file like a single array      group="[A,B,C,D,E,F]"    . But could not get something like an array representation in my question...I am looking for a 2D array representation in the xml file. 

@aemmarcCan you please advise on the steps? How can I restrict the dam folder using mime type?Is it simple like adding a property at dam folder jc:content?

Can you please advise on the steps? How can I restrict the dam folder using mime type?

So are you saying we cannot create a metadaschemavti allow only SVG images and then attach this metadata schema as a property to the specific dam folder?

This requirement is specific to one folder only. There is a component with some logos configured, business would like to upload only SVG images as logos. So we are planning to create a dedicated folder for SVG logos. So inside project dam folder, only one specific folder needs to be restricted to al...

I am also facing the same issue. But this issue we have just in production. I compared the link checker configuration and its is the same in the lower environments. I tried adding x-cq-linkchecker="skip" to the a tag. I cannot test the same in the lower environments as we don't have this issue in lo...