be worried
about it. otherwise the differences between those two wsdl-s is not
importent.
*From:* Demetris G demet...@ece.neu.edu
*To:* axis-user@ws.apache.org
*Sent:* Sunday, July 12, 2009 7:32:32 AM
*Subject:* Re: WSDL gen
:* Re: WSDL gen error
Hi again,
I am beginning to worry that (a) I am either asking a really stupid
question here
and in the thread that is listed further down in my email that is not
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am
in the wrong
list ... should
is not importent.
From: Demetris G demet...@ece.neu.edu
To: axis-user@ws.apache.org
Sent: Sunday, July 12, 2009 7:32:32 AM
Subject: Re: WSDL gen error
Hi again,
I am beginning to worry that (a) I am either asking a really stupid question
here
and in the thread
*To:* axis-user@ws.apache.org
*Sent:* Sunday, July 12, 2009 7:32:32 AM
*Subject:* Re: WSDL gen error
Hi again,
I am beginning to worry that (a) I am either asking a really stupid
question here
and in the thread that is listed further down in my email that is not
worth wasting
any time on (b
Hi again,
I am beginning to worry that (a) I am either asking a really stupid
question here
and in the thread that is listed further down in my email that is not
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am in
the wrong
list ... should I move these
Hi all,
Calling a service on the same machine as the axis server will set the
namespace
wsdl:definitions targetNamespace=http://127.0.0.1:8080/axis/services/
However, calling it from another node in the same network behind a NAT still
returns the same IP address in the name space - is that
At least someone may know this - what would cause the Axis engine to
generate WSDLs
with types instead of wsdl:types? If I know that then I can probably
figure out why
the same Axis engine distribution on two different Linux boxes would
generate two different
types of WSDLs - I am using the
And scanning through the two WSDL files I see also other diffs -
wsdl:message name=mainRequest
wsdl:part name=args type=impl:ArrayOf_soapenc_string/
/wsdl:message
vs.
wsdl:message name=mainRequest
wsdl:part name=args type=intf:ArrayOf_soapenc_string/
/wsdl:message
So it seems to me that it
And a follow up -
same Axis engine (running in exactly same OSGi containers, same
services, on one
Linux machine it generates the WSDL file with types and the other with
wsdl:types !
Why is that the case? This is a bit puzzling.
Thanks very much in advance
Demetris G wrote:
Hi all,
I am still stuck on this one - any hints would be greatly appreciated.
Thanks again
Demetris G wrote:
And a follow up -
same Axis engine (running in exactly same OSGi containers, same
services, on one
Linux machine it generates the WSDL file with types and the other
with wsdl:types !
Why
10 matches
Mail list logo
