OSB: XOP/MTOM support does not work as expected
Hi all,
we want to call a webservice which is not able to use MTOM for attachments. The attachments have to be inlined in the request. The webservice consumer sends the request with MTOM to OSB.
In the proxy service we have a XSLT transformation for our request. We are using binary by value option for the "XOP/MTOM Support" setting in proxy and business service. This setting works, but now we have the problem that transformation of the attachments takes a lot of time and uses so much heap memory that we frequently are out of memory with OSB. The maximum size of one attachment is 2MB, maximum size of all attachments is 4MB.
In my opinion there should be a possibility to transform the request without the attachment (binary by reference in the proxy) and then inline it in the business service (binary by value in the business service). But this does not work.
Additionally we tried to disable XOP/MTOM Support in business service, but this did also not work.
Our third idea was to use a binary-by-reference proxy which does the transformation. This proxy sends the message to a second proxy with binary by value setting, which finally sends the message to the business service (binary by value). Even in that scenario it did not work. That means the attachment was not inlined into the request.
The documentation in OSB userguide is not completely clear to me for that XOP/MTOM support setting, therefore I am asking for your help.
Thanks for all your ideas and advices!
Best regards,
Katja