It was pretty easy once I got the Xml structure correct.
Hope this helps
Bruce
-Original Message-
From: Mike Thomsen [mailto:mikerthom...@gmail.com]
Sent: Saturday, March 24, 2018 4:17 AM
To: dev@nifi.apache.org
Subject: Re: SOAP Service through InvokeHTTP
Been a while since I've done any
Been a while since I've done anything with SOAP, but the way I remember it
is it's just a POST operation with a XML payload at the end of the day. If
you have configured the endpoint properly in the processor's URL property
and set it to do a POST, the *flowfile content* should be where you put
I've only just subscribed to the dev@nifi.apache.org mailing list and today
was my first time even knowing that a thing like 'maling lists' existed.
Regardless, I'm posting my question in hopes to seek out how you eventually
managed to get your InvokeHTTP Processor to work with SOAP as I have not
how can i read data from soap service. What are the configuration properties
and where can i set the soap url and wsdl url uisng invokehttp?
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Hi Andrew,
I am unable to use the NiFi-soap with the latest version of nifi (1.1.0).
after build and deploying nar file to lib when I restart nifi it doesn't
start. bootstrap log tail has following:
2016-12-15 01:25:05,216 INFO [main] org.apache.nifi.bootstrap.Command
Working Directory:
Hi Jeff,
I am unable to use the NiFi-soap with the latest version of nifi (1.1.0).
after build and deploying nar file to lib when I restart nifi it doesn't
start. bootstrap log tail has following:
2016-12-15 01:25:05,216 INFO [main] org.apache.nifi.bootstrap.Command
Working Directory:
Glad it worked for you!
On Wed, Aug 24, 2016 at 8:10 PM Andrew Psaltis
wrote:
> Hello,
> I have written a SOAP processor [1] that you are free to use. It has gotten
> a bit of testing under it's belt, however, it can always use more. I am
> totally open to fixing
Hello,
I have written a SOAP processor [1] that you are free to use. It has gotten
a bit of testing under it's belt, however, it can always use more. I am
totally open to fixing issues you may find and/or accepting PR's. If it
makes enough sense and is complete enough I have no problem
Hello,
With InvokeHTTP, you can add dynamic properties, which will be sent in the
request as headers. You can use dynamic properties to set values for the
Content-Type and SOAPAction headers, just use the header names for the
names of the dynamic properties. InvokeHTTP lets you control the HTTP