Abhishek Garg created SLING-12254:
-------------------------------------
Summary: jcr:data node missing for file resources generated in
binaries index defintions
Key: SLING-12254
URL: https://issues.apache.org/jira/browse/SLING-12254
Project: Sling
Issue Type: Bug
Components: Content-Package to Feature Model Converter
Affects Versions: Content-Package to Feature Model Converter 1.3.4
Reporter: Abhishek Garg
The index definition files generated by the cpcconvertor are missing mandatory
jcr:data nodes.
How the resource should look:
{code:java}
"tika": {
"jcr:primaryType": "nam:nt:unstructured",
"config.xml": {
"jcr:primaryType": "nam:nt:file",
"jcr:content": {
"jcr:primaryType": "nam:nt:unstructured",
"jcr:mimeType": "text/xml"
}
}
}
{code}
How it looks like now:
{code:java}
"tika": {
"jcr:primaryType": "nam:nt:unstructured",
"config.xml": {
"jcr:primaryType": "nam:nt:file",
"jcr:data": "<base6_data>"
"jcr:content": {
"jcr:primaryType": "nam:nt:unstructured",
"jcr:mimeType": "text/xml"
}
}
} {code}
There is no `jcr:data` node present
This happens when node structure is like:
{code:java}
<tika jcr:primaryType="nt:unstructured">
<config.xml jcr:primaryType="nt:file" >
<jcr:content
jcr:primaryType="nt:unstructured"
jcr:mimeType="text/xml"/>
</config.xml>
</tika> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
