Hi, On Fri, Aug 21, 2015 at 7:56 PM, steven.walters <[email protected]> wrote: > ...Sure, this is basically around the importing of pre-existing content files, > so the following is pretty minimal...
Your example didn't make it to the list but it's on nabble.com, here it is: <?xml version="1.0" encoding="UTF-8"?> <node xmlns:nt="http://www.jcp.org/jcr/nt/1.0";> <name>import-content-sling</name> <primaryNodeType>nt:unstructured</primaryNodeType> <nodes> <nt:file src="file:/C:/test/sling/content/image1.png" mimeType="image/png" lastModified="2015-08-20T19:22:49-0400"/> <nt:file src="file:/C:/test/sling/content/video1.mp4" mimeType="video/mp4"/> </nodes> </node> > > I would expect that these files be imported into the JCR without issue or > complication creating correspondingly named nodes (image1.png and > video1.mp4), > but instead the condition at > *org.apache.sling.jcr.contentloader.internal.readers.XmlReader:246* fails, > causing the "/file element encountered when xml location isn't known. > skipping./" warning message to be triggered instead. > > The /xmlLocation/ is null because this operation is being triggered via the > /parse(InputStream ins, ContentCreator creator)/ call, due to being called > through the SlingPostServlet's ImportOperation mechanism. > I don't remember off the top of my head exactly how this is supposed to work now, will have a look later this week unless someone beats me to it. -Bertrand
