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 question here.
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.
I have a string array as below. String group =
I need to create a OSGI configuration property holding this value. Is it
possible? Does OSGI support this?Can we create this kind of array
configuration in OSGI?
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 allow only SVG images. So don't think amending workflow
will help here
I am looking to create a folder in DAM and impose restriction to it such
that we can add only SVG images to it. Hence I am trying to create a
metadataschema which allows only svg in images and planning to add this
as 'metadataSchema' property to my DAM folder so that this restriction
is in place.Can some one help me how I can create a metadataschema which
will allow only svg as image?We already have a metadataschema which
allows jpeg and tiff. Can I create a copy of that? If so, what changes
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 lower environments. This attribute is not
getting displayed in the a tag using DOM explorer. Is that expected?
Will we not see this parameter in the DOM Explorer? Can some one help?
I am also facing the same issue. I tried the above fix and it is not
working for me. I am using 6.3 version. Do we have a 6.3 version for the
same issue? When I click the source editor back and firth, I am loosing
the links in the content. Same issue as this one in 6.3 multi field rich