axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russell Butek" <bu...@us.ibm.com>
Subject RE: Clash Testcase Changes
Date Wed, 22 May 2002 17:33:34 GMT
Yay!  That means some of the few-and-feeble checks we have in our code can
be removed in time.  Greg.  Any ETA for the validation?

Russell Butek
butek@us.ibm.com


Greg Truty/Austin/IBM@IBMUS on 05/22/2002 11:39:16 AM

Please respond to axis-dev@xml.apache.org

To:    axis-dev@xml.apache.org
cc:
Subject:    RE: Clash Testcase Changes



The change (error recognition) is being incorporated into WSDL4J (according
to one of the WSDL4J developers)...  That's how the error was found
originally.

Regards...Greg





                      Glen Daniels
                      <gdaniels@macrom         To:
                      "'axis-dev@xml.apache.org'"
                      edia.com>                <axis-dev@xml.apache.org>
                                               cc:
                      05/22/2002 10:59         Subject: RE: Clash Testcase
                      Changes
                      AM
                      Please respond
                      to axis-dev







So in other words we dealt with even more ambiguity than is allowed by
WSDL?  Cool!  Should we (or WSDL4J?) be checking for this when parsing the
WSDL?

--G
 -----Original Message-----
 From: R J Scheuerle Jr [mailto:scheu@us.ibm.com]
 Sent: Wednesday, May 22, 2002 10:22 AM
 To: axis-dev@xml.apache.org
 Subject: Clash Testcase Changes


 The WSDL4J folks informed us that the test/wsdl/clash.wsdl file is
 invalid.

 According to WSDL 2.4.5 "The name attribute of the input and output
 elements provices a unique name among all input and output elements within
 the enclosing port type".

 I am making changes to the clash testcase to comply.

 FYI,

 Rich Scheuerle
 XML & Web Services Development
 512-838-5115  (IBM TL 678-5115)





Mime
View raw message