Hi Lars,
thanks for the response and the info regarding the namespace. My
issue is the following -
We have the Axis (1.4) bundles running in the OSGi container on a set of
Linux machines with
no issues. Web Services can be published and invoked upon - the WSDL
files that are generated
by these Axis bundles are correct and they can generate correct
operational stubs.
We needed to run a few of these on some powerful mobile devices that can
actually run Jalimo,
a full version (for fhe most part) of Java 1.5 based on the GNU
libraries. So we simply installed
the same OSGi container and Axis (1.4) bundles on them and ran them. The
Axis servers work
as they should, the generate WSDL files when invoked - however, the WSDL
file they generate
encaplsulate the scheme definitions in <types> tags instead of
<wsdl:types> ! This is an issue
because the XML parsers that process <wsdl:types> tags nicely have a
problem with the <types>
tags.
After hours of searching I came upon this -
http://issues.apache.org/jira/browse/AXIS-2336.
Others a while back have encountered the same issue when running Axis on
particular containers.
However, (a) their resolution is specific to their container (b) my
issue is not the type of container
since the OSGi container works fine with Axis. My issue is that I moved
more a Linux desktop
to a Linux mobile device, even though the executables and runtime
remained the same.
I know that Axis 1.4 is ancient, however, there are still many of them
in production and migration
for us is in our future plans but for now we need to get this to work.
Any ideas would be greatly
appreciated.
Regards
Lars Ericsson wrote:
HI Demtirs!
I couldn't understand what is your problem, please describe more about
your problem.
The namespace can be anything, and it is nothing to do whit network,
connection or anything else.
Please read more about namespace.
but if you get two different wsdl from two different environment,
sound strange, alse i suppose you have the same axis-version same-java
version and so on.
Please check manually call any service on those two service, if you
don't get the same respons, it is some thing you should be worried
about it. otherwise the differences between those two wsdl-s is not
importent.
------------------------------------------------------------------------
*From:* Demetris G <[email protected]>
*To:* [email protected]
*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) 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
> 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>
>>>
>>> ...
>>> </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
>>>>>>
>>>>>
>>>>
>>>
>>
>
