This content has been marked as final. Show 3 replies
There are two ways to do this, by embedding the attachment as an element using base64 or hexadecimal encoding, or using SOAP with attachment (MIME or DIME). The first method normally only is used when you want to be able to manipulate the attachment. Better performance is achieved with the second approach.
You can find more information in chapter 3 of the the BPEL Developers Guide:
Thanks for the response.
Assuming that I am taking the first approach of using base64binary encoding to receive attachment and also assuming I am not converting base64 into any other format(not manipulating the data), can this approach work effectively for the attachment of size between 20 to 25 MB ?
Also what could be the maximum recommended size of the attachment in this case?
The only way to find out is by testing. Mind that the attachment needs to be encoded to base64 before sending the request and at the other side needs to be decoded again. When that is going to be a problem greatly depends on the capacity of the machine doing this. I did some investigation once and was informed that for one project they saw a significant performance degradation after 5 Mb.