David- Well, the library stack wasn't really written to be released into the wild like that. I do what Mark Smith does: put templates into custom properties and then retrieve them and replace parameters.
constant kWSURL= "https://webservice.com/ws/activations.asmx" constant kWSNamespace= "http://authority.com/namespace" ON PerformAction pAction local tPartnerKey local tRegCode local tParams local tHeader put empty into field "fldResults" put empty into field "fldResponse" put empty into field "fldSOAP" put field "fldPartnerKey" into tPartnerKey put field "fldRegCode" into tRegCode put PackageParameters("Key", tPartnerKey, "string") into tHeader put PackageParameters("AuthenticationHeader", tHeader, "", kWSNamespace) into tHeader put PackageParameters("ActivationCode", tRegCode, "string", kWSNamespace) into tParams TRY put SOAP.RPCRequest(kWSURL, \ pAction, \ kWSNamespace, \ tParams, \ "http://webservice.com/ws/" & pAction, \ tHeader \ ) into field "fldResponse" put SOAP.Response() into field "fldResults" put SOAP.Envelope() into field "fldSOAP" CATCH e -- this is here for timeouts answer e END TRY END PerformAction where the custom property uSOAPEnvelope of the library stack ($HEADER, $METHOD, and $PARAMS will be replaced in the call to SOAP.RPCRequest by the appropriate parameters) is: <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header> <$HEADER> </SOAP-ENV:Header> <SOAP-ENV:Body> <$METHOD><$PARAMS/></$METHOD> </SOAP-ENV:Body> </SOAP-ENV:Envelope> (...and obviously you'll need to know the proper parameters from the wsdl...) Hope this helps. For me the hardest part was figuring out the proper authentication header format, and I only got that right by ngrepping the network traffic. -- Mark Wieder [EMAIL PROTECTED] _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution