Thanks a lot Aldrin about the details. I will look into it.
Thanks a lot. On Thu, Aug 24, 2017 at 7:24 AM, Aldrin Piri <[email protected]> wrote: > Hi Raman, > > InvokeHTTP can send data of any format. The issue at hand is that > specifying a content type does not performa any transformation of the > source flowfile content to transmit. Rather, this is just establishing the > Content-Type header. To that end, what you are seeking is certainly > possible but may not work out of the box. I am not familiar with the > format you have listed above, but the approach would be to get your payload > in the appropriate format for your endpoint. > > Doing some quick searching around it seems like this may be possible via a > custom processor to meet the contract established with these binary > endpoints for the Windows Communication Foundation (WCF). I am not overly > familiar with the constructs of WCF but certainly seems to be heavily > nested in C# which could be a challenge. It seems there are some Java > libraries tailored toward that interoperability inclusive of Metro ( > https://javaee.github.io/metro/) and Metro WSIT (https://javaee.github.io/ > metro-wsit/). These appear to be worth exploring to make the change to > the new endpoint configuration. > > On Wed, Aug 23, 2017 at 12:28 PM, Ramaninder Singh Jhajj < > [email protected]> wrote: > >> Hi All, >> >> I have a scenario. I am using invokeHTTP processor to call some endpoints >> which are working with content type "application/soap+xml;charset=UTF-8" >> but now we are moving to Binary Compressed Endpoints in which the content >> type should be *"*application/soap+msbin1+gzip". >> >> >> I am trying to make it work by changing the meme.type header to the >> required one but unfortunately it is giving bad request error. So my >> question is >> >> 1. Can invokeHTTP processor send data with binary encoding or can it only >> send with text encoding? >> 2. If it is possible, can you please give me some example how to do it? >> >> >> Kind Regards, >> Raman >> > >
