Note that there are some explanatory texts on larger screens.

plurals
  1. POUploading files to SDL Tridion 2011 using Core Service stream upload (from Java)
    primarykey
    data
    text
    <p>To start out with, my question is based on a number of answers I have found around online, and I am hoping that someone can make a clarifying answer.</p> <p>The question very short to sum it up from my current findings: Using CoreService, it seems to be that WCF is the limitation for uploading files greater than 16,384 bytes by default. I am hoping I am just overlooking something very basic, that will allow me to upload more than just empty gif files, without having to change the server configuration, as I intend for this code to be used against multiple SDL tridion instances.</p> <hr> <p>Just to provide context and what I have found, you may not need to read all this, but since I spent quite a bit of time looking and trying various things, I figured I might as well write it down for the next person that comes across this.</p> <p>I am uploading a file, using the CoreService Stream Upload, based on this example: <a href="https://stackoverflow.com/questions/10447494/how-can-i-import-external-files-into-sdl-tridion-2011-using-core-service">How can I import external files into SDL Tridion 2011 using core service?</a></p> <p>I don't want to copy all that code, but I can successfully upload a small (empty.gif) to a temp location, using that as my basis, and I get a Windows temp file path back.</p> <pre><code>String tempFileLocationOnServer = streamUploadPort.uploadBinaryByteArray( fileName, data); </code></pre> <p>For slightly large file, a PDF of 80K, I get an exception:</p> <blockquote> <p>Error in deserializing body of request message for operation 'UploadBinaryByteArray'. The maximum array length quota (16384) has been exceeded while reading XML data. This quota may be increased by changing the MaxArrayLength property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 2461.</p> </blockquote> <p>I found this <a href="https://stackoverflow.com/questions/835114/wcf-readerquotas-settings-drawbacks">WCF readerQuotas settings - drawbacks?</a>, that seems to explain it to be an issue with WCF, and is to protect against DDOS, and that one can adjust these values.</p> <p>I am thinking 80K bytes is not a lot, I am not doing anything I cannot do via the web interface with the same credentials.</p> <p>And since the CoreService already requires username/password, I don't see why there would be DDOS issues, as the request should be rejected on the authentication, before the payload.</p> <p>I am aware alternatives such as webdav or mapping a network drive on the Tridion instance, or using an separate webserver to dump files, so I can reference them as "external" when creating the multimedia component, but I rather not have to go that route. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload