jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: SOAP Sampler Confusion
Date Wed, 31 Dec 2014 12:33:11 GMT
WSDL parsing would be nice to have, but is not essential.
It's only needed when creating a test plan, so it should definitely be optional.

How much integration would actually be needed with JMeter?
For example, if its existing CLI tools can produce a text file or
clipboard entry with the extracted info, that might be enough.
In which case only documentation would be needed.

Apps that integrate every single possible feature into them become
bloated and hard to maintain and use.

On 31 December 2014 at 11:03, Philippe Mouawad
<> wrote:
> On Wed, Dec 31, 2014 at 11:56 AM, Pascal Schumacher <
>> wrote:
>> Hi Philippe,
>> Am 31.12.2014 um 11:17 schrieb Philippe Mouawad:
>>> Soap sampler is indeed deprecated in favor of plain Http Sampler, see
>>> menu
>>> Templates > Soap Webservice
>>> ImHO, SOAP/XML-RPC Request should follow the same way soon as it is just
>>> redundant with plain http sampler and less performant and up to date.
>> thanks for the quick reply. :=)
>>> But your contribution could be added to a jmeter menu (under function
>>> helper dialog for example), you would enter wsdl url or path and could
>>> generate requests from the method you select.
>>> If this feature would allow generating soap xml from wsdl then it would be
>>> very interesting.
>> That would be the point.
>> From
>> create-soap-request-template.htm
>> "The Membrane SOA Model can create SOAP request Templates out of a WSDL
>> document, filled with sample data in respect to their type definition."
>>  You can open a bugzilla and attach your patch.
>>> ask for help if needed.
>>> Check before that membrane can be included in Apache project and the jars
>>> are located on maven repositories.
>> From
>> "License
>> The Membrane SOA Model software is provided under the terms of the Apache
>> License Version 2.0. The software contains external components and
>> libraries. See the notice regarding external components in the distribution
>> archives."
>> So the license should be o.k.. I did not see any non-Apache-license
>> dependencies, so that should be o.k. too.
>> Sadly the jars are not available via maven central or any other maven
>> repository that I'm aware of, so I guess this adding this to JMeter will
>> have to wait. I will contact the developers and suggest publishing to maven
>> central.
> Too bad :-(
> Maybe this can be mitigated. From my side I see no objection to not having
> the JAR in maven repository as this feature would be kind of plugin, not
> critical for JMeter to run. Users who depend on maven builds could still
> run tests without having these jars in classpath.
> But opinion of other members is welcome.
> In the past we had a problem with RSyntaxTextArea which finally got
> published as maven artifact but it was more important dependency.
>> Regards,
>> Pascal
> --
> Cordialement.
> Philippe Mouawad.

View raw message