|
Thanks Anne! That seems to have fixed whatever the issue was.
I still have a very slow client though (which is the core problem)… I’m looking for sub-second or a second and some change response time for the entire run (including JVM load time, or .Net load time), and it’s taking anywhere from 6-12 seconds to perform the web service call. The actual code that I’m calling takes a few tenths of a second (I’ve got time print-outs confirming this).
Any ideas on how to drop my response time down dramatically? It maybe unreasonable to ask for sub-second response time, but if so I’d at least like to know before I do much more development with web services.
Thank you, Paul Lessard
From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED]
Try generating the
service as style="WRAPPED". On 2/22/06, Lessard, Paul <[EMAIL PROTECTED] > wrote: All,
I got my web service working fine in Axis 1.3 by using the jws instant deployment. Data was going to and coming from the service just fine. The default on the instant deploy appears to be RPC based, so I wanted to deploy it out as doc / lit using the wsdd deployment file. I have data going to the service, I can see the service process the data, and the returned String variable is populated with data. The issue is, however, when I return the populated String from the web service, the data comes back as null or "" in both a .Net and a Java client (both auto generated from wsdl). Here is the wsdl:
<?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions targetNamespace="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl=" http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:intf="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:tns1="http://DefaultNamespace" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <!--WSDL created by Apache Axis version: 1.3 Built on Oct 05, 2005 (05:23:37 EDT)--> <wsdl:types> <schema elementFormDefault="qualified" targetNamespace="http://DefaultNamespace" xmlns=" http://www.w3.org/2001/XMLSchema"> <element name="in0" type="xsd:string"/> </schema> <schema elementFormDefault="qualified" targetNamespace="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns="http://www.w3.org/2001/XMLSchema"> <element name="processDictaphoneReturn" type="xsd:string"/> </schema> </wsdl:types>
<wsdl:message name="processDictaphoneRequest">
<wsdl:part element="tns1:in0" name="in0"/>
</wsdl:message>
<wsdl:message name="processDictaphoneResponse">
<wsdl:part element="impl:processDictaphoneReturn" name="processDictaphoneReturn"/>
</wsdl:message>
<wsdl:portType name="Dictaphone">
<wsdl:operation name="processDictaphone" parameterOrder="in0">
<wsdl:input message="impl:processDictaphoneRequest" name="processDictaphoneRequest"/>
<wsdl:output message="impl:processDictaphoneResponse" name="processDictaphoneResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DictaphoneSoapBinding" type="impl:Dictaphone">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="processDictaphone">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="processDictaphoneRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="processDictaphoneResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="DictaphoneService">
<wsdl:port binding="impl:DictaphoneSoapBinding" name="Dictaphone">
<wsdlsoap:address location="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Is there any other information I can supply? Again, it does return data using the instant deploy, and in both the instant deploy AND the doc / lit wsdd version data get to the web service.
Thank you, Paul Lessard
|
