axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@watson.ibm.com>
Subject Re: WSDL4J bug
Date Tue, 22 Jan 2002 23:22:09 GMT
I agree with Simon; WSDL's definitions of import is not that of
#include in C - its that of import in XSD. As such, <wsdl:import>
only establishes place where *somethings* related to the indicated
namespace could be found.

Sanjiva.

----- Original Message -----
From: "Simon Fell" <soap@zaks.demon.co.uk>
To: <axis-dev@xml.apache.org>
Sent: Wednesday, January 23, 2002 4:00 AM
Subject: Re: WSDL4J bug


> That depends on how you're processing imports. If you treat them as
> pure textual imports you run into 2 potential problems (i) imports
> that referer to schemas are missing the wrapping <types> element, (ii)
> you can get stuck in a loop doing circular imports.
>
> Cheers
> Simon
>
> On Tue, 22 Jan 2002 15:53:56 -0600, in soap you wrote:
>
> >That may be true, BUT when you consider imports, you could end up with
this
> >same order anyway.  Consider the following pseudo-wsdl:
> >
> >File1:
> ><import "File2">
> ><message...>
> >
> >File2:
> ><import "File3">
> ><portType...>
> >
> >File3:
> ><import "File4">
> ><binding...>
> >
> >None of these files, by themselves, are illegal.  In File1 we see File2,
so
> >we go into that before processing the rest of File1.  In File2 we see
File3
> >so we go into that before processing the rest of File2.  Etc.  So the
> >processing order is:  binding, portType, message.
> >
> >Russell Butek
> >butek@us.ibm.com
> >
> >
> >Simon Fell <soap@zaks.demon.co.uk> on 01/22/2002 03:36:43 PM
> >
> >Please respond to axis-dev@xml.apache.org
> >
> >To:    axis-dev@xml.apache.org
> >cc:
> >Subject:    Re: WSDL4J bug
> >
> >
> >
> >On Tue, 22 Jan 2002 15:06:21 -0500, in soap you wrote:
> >
> >>Matt, I think I sent you this first bug before, but I have another
> >>variation, now...
> >>
> >>
> >>1.  When the stanzas are in reverse order -
> >><binding...><portType...><message...> -  a call to
portType.getOperations
> >>().iterator() will return an iterator which returns all operations
twice.
> >>This wsdl and test program show the problem:  (See attached file:
> >>duplicate.wsdl), (See attached file: Test.java).
> >
> >That's not legal WSDL, the spec and schema both define a fixed order
> >of import, message, portType, binding, service. You should fault if
> >the order is wrong.
> >
> >Cheers
> >Simon
> >


Mime
View raw message