Bertrand Delacretaz wrote >> ...as a result, this completely blocks being able to have absolute URLs >> in >> the imported XML content in this scenario... > > Could you provide a minimal example of what doesn't work for you? > > Maybe an example XML file, indicating what doesn't match your > expectations after importing.
Sure, this is basically around the importing of pre-existing content files, so the following is pretty minimal. 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. -- View this message in context: http://apache-sling.73963.n3.nabble.com/Further-clarification-of-SLING-2512-tp4053816p4053833.html Sent from the Sling - Users mailing list archive at Nabble.com.
