RE: No data back on doc / lit based wsdl generated code - Response Time Still Too High
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] Sent: Wednesday, February 22, 2006 4:21 PM To: axis-user@ws.apache.org Subject: Re: No data back on doc / lit based wsdl generated code Try generating the service as style="WRAPPED". Anne 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: 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"> http://DefaultNamespace" xmlns=" http://www.w3.org/2001/XMLSchema"> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns="http://www.w3.org/2001/XMLSchema"> http://schemas.xmlsoap.org/soap/http"/> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone"/> 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
No data back on doc / lit based wsdl generated code
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: 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
RE: Axis2 interoperability with .Net
Anne,
I’m using 0.94 of Axis2, and I
basically followed the first example on the User Guide. I just deployed
out the axis2.war to my tomcat server, and posted a WebService in an aar
file. The aar has the compiled code with 1 exposed method, and a
services.xml in the META-INF subdir of the aar. Here is the services.xml:
This is a sample Web Service with two operations,echo and ping.
AdmitToDplWebService
The publicly exposed method is the
following:
public OMElement admitToDpl(OMElement
admitNumbers)
{
OMElement
dplCodes = null;
try
{
dplCodes
= setupReturnDocument();
Vector
v = getDplCodes(admitNumbers);
addDplCodes(dplCodes,
v);
}catch(Exception
e)
{
System.err.println(“(admitToDpl):
Could not retrieve a list of DPL codes for the passed in numbers. “+e);
}
Return
dplCode;
}
The remaining code I don’t believe
is relevant, but I can supply it if you need. The code does compile, and
the web service works perfectly when using the axis2 EchoBlockingClient.java
skeleton to access the web service. Is there any more information I can
provide?
Thank you,
Paul Lessard
From: Anne Thomas
Manes [mailto:[EMAIL PROTECTED]
Sent: Monday, February 13, 2006
3:26 PM
To: axis-user@ws.apache.org
Subject: Re: Axis2
interoperability with .Net
What version of Axis2 are
you using?
The generated WSDL has errors in it. All the schema attributes have been
namespace qualified, but they should not be. e.g.,
should be:
Can you tell us what you did to generate the WSDL?
Anne
On 2/13/06, Lessard,
Paul <[EMAIL PROTECTED]>
wrote:
Hi
all,
I'm
trying to use the wsdl.exe prog provided by the .Net SDK and I'm getting some
errors. Looking through past posts, this doesn't seem to be the
"tn1" name problem that others had. The error I'm getting is
the following:
Schema
validation warning: The required attribute 'name' is missing.
Schema
validation warning: For element declaration either the name or the ref
attribute must be present.
Schema
validation warning: The required attribute 'name' is missing.
Schema
validation warning: For element declaration either the name or the ref
attribute must be present.
Warning:
Schema could not be validated. Class generation may fail or may produce
incorrect results.
Error:
Unable to import binding 'AdmitToDplBinding' from namespace 'http://org.apache.axis2/'.
- Unable to import operation 'admitToDpl'.
- The element 'http://org.apache.axis2/xsd:admitToDplRequest' is missing.
I'm
just starting out in Web Services, so I'm not very familiar with WSDL
files. Having said that, here is the auto-generated WSDL from Axis2
(sorry it isn't spaced out nicely):
http://org.apache.axis2/xsd"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="
http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://org.apache.axis2/"
targetNamespace="http://org.apache.axis2/">http://www.w3.org/2001/XMLSchema"
xmlns:ns2="http://www.w3.org/2001/XMLSchema"
xmlns:ns0="http://www.w3.org/2001/XMLSchema"
xmlns:ns1="http://www.w3.org/2001/XMLSchema"
ns1:elementFormDefault="qualified"
ns0:attributeFormDefault="unqualified" ns2:targetNamespace="http://org.apache.axis2/xsd">
http://schemas.xmlsoap.org/soap/http"
style="document" />http://www.org.apache.axis2"
/>http://www.org.apache.axis2"
/>http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone"
/>
Anybody
have any ideas? It's probably something blindingly obvious, but as said,
I'm quite new to Web Services.
Thank
you,
Paul
Lessard
RE: Axis2 interoperability with .Net
All, Sorry... just noticed I pasted the wrong wsdl.exe dump for the WSDL I sent below. The proper wsdl.exe dump is: Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 1.1.4322.573] Copyright (C) Microsoft Corporation 1998-2002. All rights reserved. Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'DictaphoneBinding' from namespace 'http://org.apache.axis2/'. - Unable to import operation 'processDictaphone'. - The element 'http://org.apache.axis2/xsd:processDictaphoneRequest' is missing. Thanks for your help, Paul Lessard P.S. SOA Editor is no longer available from Cape Clear. They replaced SOA with "Cape Clear Studio" which I believe costs money. There maybe links to archived versions of SOA somewhere but I haven't found any yet. -Original Message- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: > Hi all, > > > > I'm trying to use the wsdl.exe prog provided by the .Net SDK and I'm > getting some errors. Looking through past posts, this doesn't seem to > be the "tn1" name problem that others had. The error I'm getting is the > following: > > > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > > > Warning: Schema could not be validated. Class generation may fail or may > produce incorrect results. > > > > Error: Unable to import binding 'AdmitToDplBinding' from namespace > 'http://org.apache.axis2/'. > > - Unable to import operation 'admitToDpl'. > > - The element 'http://org.apache.axis2/xsd:admitToDplRequest' is > missing. > > > > > > > > I'm just starting out in Web Services, so I'm not very familiar with > WSDL files. Having said that, here is the auto-generated WSDL from > Axis2 (sorry it isn't spaced out nicely): > > > > http://org.apache.axis2/xsd"; > xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:tns="http://org.apache.axis2/"; > targetNamespace="http://org.apache.axis2/";> xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:ns2="http://www.w3.org/2001/XMLSchema"; > xmlns:ns0="http://www.w3.org/2001/XMLSchema"; > xmlns:ns1="http://www.w3.org/2001/XMLSchema"; > ns1:elementFormDefault="qualified" > ns0:attributeFormDefault="unqualified" > ns2:targetNamespace="http://org.apache.axis2/xsd";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="processDictaphoneResponseMessage"> element="ns1:processDictaphoneResponse" /> name="processDictaphoneRequestMessage"> element="ns1:processDictaphoneRequest" /> name="DictaphonePort"> name="processDictaphone"> message="tns:processDictaphoneRequestMessage" /> message="tns:processDictaphoneResponseMessage" > /> name="DictaphoneBinding" type="tns:DictaphonePort"> transport="http://schemas.xmlsoap.org/soap/http"; style="document" > /> name="operation" soapAction="processDictaphone" style="document" > /> namespace="http://www.org.apache.axis2"; > /> namespace="http://www.org.apache.axis2"; > /> name="Dictaphone"> binding="tns:DictaphoneBinding"> location="http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone"; > /> > > > > > > Anybody have any ideas? It's probably something blindingly obvious, but > as said, I'm quite new to Web Services. > > > > Thank you, > > Paul Lessard --
RE: Axis2 interoperability with .Net
Robert, Thank you for your help. What is "doc / lit" if you don't mind me asking? Also, are you using the auto-generated wsdl files from the axis2 primary API's or are you creating a WSDL and generating Java code from that? My WSDL file is auto-generated by Axis2, so I don't know how much control I have over editing the WSDL file. Thank you, Paul Lessard -Original Message- From: robert [mailto:[EMAIL PROTECTED] Sent: Monday, February 13, 2006 12:50 PM To: axis-user@ws.apache.org Subject: Re: Axis2 interoperability with .Net I do have some axis2 web services and web services clients between java and net, so it is possible. You using doc / lit - good. Try the 'free as in beer' soa editor from cape clear - it found 5 errors ;-) . HTH, Robert http://www.braziloutsource.com/ Em Segunda 13 Fevereiro 2006 16:35, o Lessard, Paul escreveu: > Hi all, > > > > I'm trying to use the wsdl.exe prog provided by the .Net SDK and I'm > getting some errors. Looking through past posts, this doesn't seem to > be the "tn1" name problem that others had. The error I'm getting is the > following: > > > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > Schema validation warning: The required attribute 'name' is missing. > > Schema validation warning: For element declaration either the name or > the ref attribute must be present. > > > > Warning: Schema could not be validated. Class generation may fail or may > produce incorrect results. > > > > Error: Unable to import binding 'AdmitToDplBinding' from namespace > 'http://org.apache.axis2/'. > > - Unable to import operation 'admitToDpl'. > > - The element 'http://org.apache.axis2/xsd:admitToDplRequest' is > missing. > > > > > > > > I'm just starting out in Web Services, so I'm not very familiar with > WSDL files. Having said that, here is the auto-generated WSDL from > Axis2 (sorry it isn't spaced out nicely): > > > > http://org.apache.axis2/xsd"; > xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > xmlns:tns="http://org.apache.axis2/"; > targetNamespace="http://org.apache.axis2/";> xmlns:xs="http://www.w3.org/2001/XMLSchema"; > xmlns:ns2="http://www.w3.org/2001/XMLSchema"; > xmlns:ns0="http://www.w3.org/2001/XMLSchema"; > xmlns:ns1="http://www.w3.org/2001/XMLSchema"; > ns1:elementFormDefault="qualified" > ns0:attributeFormDefault="unqualified" > ns2:targetNamespace="http://org.apache.axis2/xsd";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > name="processDictaphoneResponseMessage"> element="ns1:processDictaphoneResponse" /> name="processDictaphoneRequestMessage"> element="ns1:processDictaphoneRequest" /> name="DictaphonePort"> name="processDictaphone"> message="tns:processDictaphoneRequestMessage" /> message="tns:processDictaphoneResponseMessage" > /> name="DictaphoneBinding" type="tns:DictaphonePort"> transport="http://schemas.xmlsoap.org/soap/http"; style="document" > /> name="operation" soapAction="processDictaphone" style="document" > /> namespace="http://www.org.apache.axis2"; > /> namespace="http://www.org.apache.axis2"; > /> name="Dictaphone"> binding="tns:DictaphoneBinding"> location="http://fh2k039.fhmis.net:8080/axis2/services/Dictaphone"; > /> > > > > > > Anybody have any ideas? It's probably something blindingly obvious, but > as said, I'm quite new to Web Services. > > > > Thank you, > > Paul Lessard --
Axis2 interoperability with .Net
Hi all, I’m trying to use the wsdl.exe prog provided by the .Net SDK and I’m getting some errors. Looking through past posts, this doesn’t seem to be the “tn1” name problem that others had. The error I’m getting is the following: Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Schema validation warning: The required attribute 'name' is missing. Schema validation warning: For element declaration either the name or the ref attribute must be present. Warning: Schema could not be validated. Class generation may fail or may produce incorrect results. Error: Unable to import binding 'AdmitToDplBinding' from namespace 'http://org.apache.axis2/'. - Unable to import operation 'admitToDpl'. - The element 'http://org.apache.axis2/xsd:admitToDplRequest' is missing. I’m just starting out in Web Services, so I’m not very familiar with WSDL files. Having said that, here is the auto-generated WSDL from Axis2 (sorry it isn’t spaced out nicely): Anybody have any ideas? It’s probably something blindingly obvious, but as said, I’m quite new to Web Services. Thank you, Paul Lessard
