Already available sebb.

On Thu, Oct 3, 2013 at 2:40 PM, sebb <[email protected]> wrote:

> On 1 October 2013 22:03, Philippe Mouawad <[email protected]>
> wrote:
> > On Tue, Oct 1, 2013 at 6:36 PM, sebb <[email protected]> wrote:
> >
> >> On 1 October 2013 11:24, Nicola Ambrosetti Brolin
> >> <[email protected]> wrote:
> >> > Maybe it will prompt someone to add xml syntax highlighting and we
> could
> >> > dream of one day finally being able to generate a soap request from
> the
> >> > wsdl? Then I could finally drop soapUI ;-)
> >>
> >> Not sure that syntax highlighting is sufficient, but if it is, that
> >> should be easy now that we are using RSyntaxTextArea.
> >>
> >> When I last looked, there did not seem to be a stand-alone WSDL parser
> >> with a suitable license. The existing WSDL parser is extremely basic
> >> and only supports very simple WSDL files.
> >>
> >> >
> >> > On 29 September 2013 14:20, Philippe Mouawad <
> [email protected]
> >> >wrote:
> >> >
> >> >> Hello,
> >> >> What about deprecating SOAP/XML-RPC Request ?
> >> >>
> >> >>
> >> >> It duplicates part of HTTP Sampler and uses HTTP Client 3.
> >> >>
> >> >> I don't see any reason to keep it.
> >> >>
> >> >> Thoughts ?
> >>
> >> What do the two requests look like?
> >> Is it easy to convert a general SOAP/XML-RPC Request to an HTTP request?
> >>
> >> Yes you copy past content in Raw Post Body
> > And add a Header Manager for SoapAction
> > With templates, it is now very easy.
>
> In which case, we should add a sample SOAP template or two before
> deprecating the sampler.
>
> >> >>
> >> >> --
> >> >> Regards.
> >> >> Philippe.
> >> >>
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.

Reply via email to