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 two questions to the axis-dev you think?
If axis is giving me a different WSDL file in two different Linux
machines while
the configuration and version is the same, is that a bug I need to worry
about?
And at least any information on how to manipulate the IP address in the WSDL
would be greatly appreciated.
Anyone??
Thanks once again
Demetris
Demetris G wrote:
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 normal?
Also, how can the IP address in the first case (calling it from the
same machine)
be set to the true IP address of the machine?
Also if anyone has any more info on my email below it will be greatly
appreciated.
Thanks
Demetris
Demetris G wrote:
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 treats the same service a bit differently
on a separate
machine even though the setup/config etc of the server is identical.
Demetris G wrote:
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 same browser to issue the request:
http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl
One engine gives this:
<types>
<schema targetNamespace="http://xml.apache.org/xml-soap";>
...
</types>
and the other:
<wsdl:types>
<schema targetNamespace="http://xml.apache.org/xml-soap";>
...
</wsdl:types>
Any ideas?
Thanks
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 is that the case? This is a bit puzzling.
Thanks very much in advance
Demetris G wrote:
Hi all,
this may have been asked a while back - what would cause the
Axis engine to generate
WSDLs that carry <types> instead of <wsdl:types>: This causes the
WSDL parser I use
to throw:
[java] WSDLException (at /wsdl:definitions/types):
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a
'javax.wsdl.Definition'.
Extension elements must be in a namespace other than WSDL's.:
Using Axis 1.4 over java 1.5.
Any ideas?
Thanks
