Forum Discussion
JimL
17 years agoContributor
Hi,
Thanks for the info. Mainly I was just checking because I thought that I might have missed this capability somewhere.
I was actually kind of surprised myself that the server hosting the webservice (WebLogic) cared that the namespace was not "env:", since the URL was the same for both "env:" and "soapenv:"
I am curious though, WHAT (and why) is deciding that the namespace on the request envelopes should be "soapenv:"?
Is it SOAPUI itself?
The reason for my question is that I don't see "soapenv" anywhere in the WSDL that I imported into SOAPUI, so is "soapenv" just some kind of default decision that SOAPUI makes?
Thanks again,
Jim
Thanks for the info. Mainly I was just checking because I thought that I might have missed this capability somewhere.
I was actually kind of surprised myself that the server hosting the webservice (WebLogic) cared that the namespace was not "env:", since the URL was the same for both "env:" and "soapenv:"
I am curious though, WHAT (and why) is deciding that the namespace on the request envelopes should be "soapenv:"?
Is it SOAPUI itself?
The reason for my question is that I don't see "soapenv" anywhere in the WSDL that I imported into SOAPUI, so is "soapenv" just some kind of default decision that SOAPUI makes?
Thanks again,
Jim