Expand my Community achievements bar.

SOLVED

AEM FormsService not returing binary content

Avatar

Level 2

SOAP call to AEM 6.5 is not returning Binary content it just returns the URL. The Proxy has been generated with blob=base64. What else could be the issue? 

1 Accepted Solution

Avatar

Correct answer by
Level 2

The issue was a missing patch. We implemented the patch for AEM 6.5 and updated it to 6.5.3 with the help from Adobe support and it resolved the issue. Thanks all for viewing and responding to the question.

 

Note - 6.5.3 is not directly available in the download site. Raise a SR with support and they will help you. 

View solution in original post

5 Replies

Avatar

Employee

What you describe very briefly sounds like you did not properly apply the blob=base64. What exactly do you get back from the service? Does it return the BLOB data type and the remoteURL field is set?

 

Check out this page https://help.adobe.com/en_US/livecycle/11.0/ProgramLC/WS624e3cba99b79e12e69a9941333732bac8-7fd4.2.ht...

Avatar

Level 2
The service returns the BLOB with remoteURL and the binary is returned as null

Avatar

Employee

Hi,

I think we need to drill down a bit further.

The SOAP interface basically responds depending on what the calling framework allows for.

The blob=base64 only says that the binary data is to be converted to BASE64 text - but not that it always comes back also in binaryData (although that is default). 

Check out the "Accessing data in BLOB objects returned from services" in the link I provided before. 

Under 4. it says "Otherwise. If a service does not take the document type as input, then the output documents are returned in the BLOB.remoteURL field over the HTTP protocol."

You may encounter this situation.

Avatar

Employee Advisor

@kalyan  Instead of proxy approach try to hit the endpoint for the service directly and check the response. You should be able to set the Blob Objects from adminUI

Mayank_Gandhi_0-1597258947586.png

 

Avatar

Correct answer by
Level 2

The issue was a missing patch. We implemented the patch for AEM 6.5 and updated it to 6.5.3 with the help from Adobe support and it resolved the issue. Thanks all for viewing and responding to the question.

 

Note - 6.5.3 is not directly available in the download site. Raise a SR with support and they will help you.