Is my WSDL insane, or is it me?
I am evaluating SoapUI Pro for use with a Retail Transaction Interface-based service.
I am new to testing SOAP services, and certainly new to SoapUI, so I suspect this is user error, just for some background.
It is a WCF service compiled to run as a Windows service.
I was able to get SoapUI to load up the supported interface by appending a ?wsdl to the baseAddress. . .
So in my configuration file it has a section like this:
And I used http://015BO:9001/?wsdl to get SoapUI to populate the calls out I can make.
When I attempted to click on a sample request to edit it, it took 8 minutes to get to where I could look at the fields, and there were far more fields than I'd actually need to use to do this transaction. (I probably need one or two.)
I switched to XML view and then did a count on the number of "?"s in the text, and got something like 12,000.
Clearly, something fishy is going on. Did I generate the wsdl improperly? Is it because we're using RTI as the basis for our service, and perhaps RTI allows for all kind of optional parameters for this very simple activity?
Thanks,
Jody
I am new to testing SOAP services, and certainly new to SoapUI, so I suspect this is user error, just for some background.
It is a WCF service compiled to run as a Windows service.
I was able to get SoapUI to load up the supported interface by appending a ?wsdl to the baseAddress. . .
So in my configuration file it has a section like this:
<services>
<service behaviorConfiguration="brokerBehavior" name="Matra.Freedom.Server.Broker">
<endpoint address="RTIService" binding="netTcpBinding" bindingConfiguration="TcpBrokerBinding"
name="TCPRTIService" contract="HostServerReference.IRTIService" />
<endpoint address="Management" binding="netTcpBinding" bindingConfiguration="TcpBrokerBinding"
name="Management" contract="Matra.Freedom.Server.BrokerContracts.IBrokerManagement" />
<endpoint address="HostManagement" binding="netTcpBinding" bindingConfiguration="TcpBrokerBinding"
name="HostManagement" contract="Matra.Freedom.Server.BrokerContracts.IBrokerHostManagement" />
<endpoint address="mex" binding="mexHttpBinding" name="mex" contract="IMetadataExchange" />
<endpoint address="http://localhost:9020/RTIService" binding="basicHttpBinding"
bindingConfiguration="HttpBrokerBinding" name="HTTPBrokerBinding"
contract="HostServerReference.IRTIService" />
<host>
<baseAddresses>
<add baseAddress="net.tcp://015BO:9000/"/>
<add baseAddress="http://015BO:9001/"/>
</baseAddresses>
</host>
</service>
</services>
And I used http://015BO:9001/?wsdl to get SoapUI to populate the calls out I can make.
When I attempted to click on a sample request to edit it, it took 8 minutes to get to where I could look at the fields, and there were far more fields than I'd actually need to use to do this transaction. (I probably need one or two.)
I switched to XML view and then did a count on the number of "?"s in the text, and got something like 12,000.
Clearly, something fishy is going on. Did I generate the wsdl improperly? Is it because we're using RTI as the basis for our service, and perhaps RTI allows for all kind of optional parameters for this very simple activity?
Thanks,
Jody
