hehe, I've used SOAP, but honestly, I can't say that it's pleasurable or even good.
URL - this is required by all the webservice toolkits SOAPAction - currently, this is only required and used by microsoft's .NET Parameters - there's generally 2 preferred approach for creating the SOAPEnvelop message. 1 use objects and serialize to a valid SOAPEnvelope. 2. use a DOM object. apache SOAP took the DOM route, which many people disliked, so Axis was born. that's a gross over generalization. the easiest way to use soap is to expose a class in tomcat and the Axis framework automatically generates the WSDL, which includes the XML Schema. Unlike Apache SOAP, Axis has the ability to generate classes from the WSDL using the wsdl4j, which was donated by IBM I think. My original thought was to this. 1. user enters WSDL url 2. jmeter uses Axis to generate the java classes 3. jmeter loads the jar and then provides a drop down of the soap messages 4. user selects a soap message, which tells jmeter which objects are used 5. user provides values for the object(s) 6. the objects are passed to Axis, which serializes it to the proper SOAPEnvelope the difficulty I had was figuring out an elegant way to handle 3-5. If you have some ideas, I'm all ears :) it would be nice to do it that way, but not sure how easy it would be. peter On 12/12/05, sebb <[EMAIL PROTECTED]> wrote: > > Perhaps the way to approach this is to see what what would like to see > in the GUI, and progress from there? > > The parameters would need to include: > > URL > Soap Action > Parameters > > Not having used Soap in anger, I'm not sure what else would be > needed/useful. > > S. > On 12/12/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > the recommended method of using Axis is to use objects directly and > bypass > > XML documents. when I first started working on an Axis sampler last > year, it > > was with the goal of using objects directly. I never figured out a good > way > > to use the object approach in JMeter, so I never finished it. > > > > > > peter > > > > > > On 12/12/05, sebb <[EMAIL PROTECTED]> wrote: > > > > > > Isn't that what the current sampler does? > > > > > > Seems to me the Axis approach is to extract the variable parts and > > > provide those as parameters, rather than needing to wrap it all in > > > XML. > > > > > > S. > > > On 12/12/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > looks like if I use AXIS specific API, I may be able to create SOAP > > > messages > > > > directly from XML documents. I'll try to work on it next week and > see > > > how it > > > > goes > > > > > > > > peter > > > > > > > > > > > > On 12/9/05, sebb <[EMAIL PROTECTED]> wrote: > > > > > > > > > > The WebService(SOAP) sampler currently uses Apache SOAP, which no > > > > > longer seems to be maintained. > > > > > > > > > > Perhaps we should look at creating a new sampler that uses Apache > > > Axis? > > > > > > > > > > Looks quite simple to use: > > > > > > > > > > > http://ws.apache.org/axis/java/user-guide.html#BasicsGettingStarted > > > > > > > > > > It takes a different approach to building the Soap messages - as > far > > > > > as I can see, there is no need to mess around with XML, just need > to > > > > > provide the parameters and Axis takes care of the rest. > > > > > > > > > > Just need to decide how to provide the parameters via the GUI - > I've > > > > > not used Soap in earnest, so I don't know what would make sense > for > > > > > testing Soap. > > > > > > > > > > Sebastian > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
