I was working with the SlingPostServlet operation :import with the XML (not the JCR XML) format and came across the code that is implicated in SLING-2512.
This basically renders the entire nt:file import functionality completely blocked from utilization when going through the SlingPostServlet, as it always imports through a InputStream which as a result always has the "xmlLocation" as null. Yes, not having a base location prevents the use of relative URLs within the imported XML content, as this would result in MalformedURLException from not having a protocol. But as a result, this completely blocks being able to have absolute URLs in the imported XML content in this scenario. As this is, local file system can not be imported and separate individual uploads of the local file system content has to be utilized. This is decently inconvenient to have to manage separate uploads for all the individual files in this manner. Is there any additional detail as to why SLING-2512 is a bug exactly, in that it is classified as "should not be allowed"? - Steven
