Return-Path: 
 <axis-user-return-79693-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 65149 invoked from network); 13 Jul 2009 16:28:25 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 13 Jul 2009 16:28:25 -0000
Received: (qmail 17368 invoked by uid 500); 13 Jul 2009 16:28:33 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 17193 invoked by uid 500); 13 Jul 2009 16:28:32 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 17163 invoked by uid 99); 13 Jul 2009 16:28:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jul 2009 16:28:30 +0000
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=FM_FAKE_HELO_VERIZON,NORMAL_HTTP_TO_IP,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [206.46.173.11] (HELO vms173011pub.verizon.net) (206.46.173.11)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jul 2009 16:28:19 +0000
Received: from [129.10.56.94] by vms173011.mailsrvcs.net
 (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit))
 with ESMTPA id <0KMQ009AMB20VSH1@vms173011.mailsrvcs.net> for
 axis-user@ws.apache.org; Mon, 13 Jul 2009 11:27:37 -0500 (CDT)
Message-id: <4A5B607A.7050206@ece.neu.edu>
Date: Mon, 13 Jul 2009 12:27:38 -0400
From: Demetris G <demetris@ece.neu.edu>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-version: 1.0
To: axis-user@ws.apache.org
Subject: Re: WSDL gen error
References: <c39900360907060659o726ab4c7id3350e13ea37abe@mail.gmail.com>
 <9e2fff830907070956l4c455322i4068909e7ed6c91d@mail.gmail.com>
 <c39900360907071110r4edcb399y7e6279b9e3682e3@mail.gmail.com>
 <4A544272.7080905@ece.neu.edu> <4A544709.4060108@ece.neu.edu>
 <4A557810.9030608@ece.neu.edu> <4A56C9D2.6020507@ece.neu.edu>
 <4A56CFBB.2020308@ece.neu.edu> <4A5808FA.4050201@ece.neu.edu>
 <4A597570.40709@ece.neu.edu> <74528.14043.qm@web59811.mail.ac4.yahoo.com>
In-reply-to: <74528.14043.qm@web59811.mail.ac4.yahoo.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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 <demetris@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 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
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>