Hi. I can check with on of our developers or run a test again, but that's the combination that worked. As I understand it, without hexBinary, images were not able to be opened..
Easy enough to test again. I'll do that in the coming days and confirm Kind Regards, David Ennis David Ennis *Content Engineer* [image: HintTech] <http://www.hinttech.com/> Mastering the value of content creative | technology | content Delftechpark 37i 2628 XJ Delft The Netherlands T: +31 88 268 25 00 M: +31 63 091 72 80 [image: http://www.hinttech.com] <http://www.hinttech.com> <https://twitter.com/HintTech> <http://www.facebook.com/HintTech> <http://www.linkedin.com/company/HintTech> On 10 February 2015 at 17:07, Florent Georges <[email protected]> wrote: > On 10 February 2015 at 14:23, David Ennis wrote: > > > I just checked some of our source code for saving from a post to disk. > > Florent's example has the key - its the casting to xs:base64binary.. > > > Good to hear :-) > > > An example from working code is: xdmp:save([your-path-here], > > binary{xs:hexBinary(xs:base64Binary([your post variable here)}) > > > Mmh, that's weird you need to have > xs:hexBinary(xs:base64Binary(...)). You should be able to create a > binary node with either a hex or a base64 binary item. I do not see > need to convert the base64 one to hex (even though I don't expect it > to do any harm). > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
