soap ui request with cert in text mode
I use my soap request with client cert in text mode. how can i insert cert in the request use WSCS and WSCC parameters? Now the request look like this: <soapenv:Envelope xmlns:soapenv="...
Forum Discussion
Hey Soloway
WOW! I have NEVER seen a .wsdl so short on content - you haven't got any bindings in there - no service tag in there - no wonder you're stuck.
if you look here --> https://www.w3.org/TR/wsdl.html this is about the simplest example of a .wsdl I've seen and yours has even less content!
Ok - this is gonna be a bit of a struggle. Can you confirm who mentioned WSCS/WSCC for your SOAP service? Are you sure they're correct? If they're so sure it uses WSCS/WSCC, is there a reason why they can't give you a complete/updated .wsdl?
If you can attach the .wsdl (saves me trying to copy it out of an image manually) I can try to start and build the content I think it needs - but you're still gonna need to determine all the info required to go in the additional WSCS/WSCC tag content in your SOAP payload.
that's the best I can think of right now....unless anybody else has some decent ideas?
nice one
Rich
richielook at the attach. there a 2 files. one is the wsdl and second - xml that i receive from my colleague.
So i sent a request using that soapui-project.xml and boom, have a lot a problems. Thaks for any help
- Hey Soloway,
Sorry i didnt get a chance to look today cos worked late. Will try and get to it tomorrow.
By the way. It helps xml handling if you reflect what your files are by setting the file extensions to what the file is. I notice your .wsdl has an .xml extension. Change it to .wsdl.
likewise the schemas youve attached have .xml extensions also. Change them to .xsd. it helps certain applications soapui, xmlspy, etc. If you use the correct file extension rather than keep them all as .xml.
Its not essential, ita juat a suggestion.
Cheers
Rich
