Hi Russell,
Ok, #2 has been fixed. The following is the cvs comment from the commit: - Added logic to com.ibm.wsdl.xml.WSDLReaderImpl to take into account any input and output names when parsing portType operations and binding operations. There were 2 sections marked with "needs additional work" that have now been completed. Before these sections were completed, the reader would not handle overloaded operations correctly. Thanks to Russell Butek and Tony Hong for raising this issue. Thanks for the test program, it helped chase this down. It works fine now. Take a look here to see the changes: http://www-124.ibm.com/developerworks/oss/cvs/wsdl4j/wsdl4j/src/com/ibm/wsdl/xml/WSDLReaderImpl.java.diff?r1=1.13&r2=1.14 Thanks, -Matt Russell Butek To: Matthew Duftler/Watson/IBM@IBMUS 02/05/2002 03:06 cc: [EMAIL PROTECTED] PM From: Russell Butek/Austin/IBM@IBMUS Subject: Re: WSDL4J bug(Document link: Matthew Duftler) Any word on these bugs, Matt? Particularly #2, overloaded operations; I've gotten a couple pings from AXIS users about it. Russell Butek [EMAIL PROTECTED] MATTHEW DUFTLER 01/25/2002 12:58 PM To: Russell Butek/Austin/IBM@IBMUS cc: [EMAIL PROTECTED] From: Matthew Duftler/Watson/IBM@IBMUS Subject: Re: WSDL4J bug (Document link: Russell Butek) Hi Russell, Just wanted to let you know that I got your email. I'll take a look at these bugs shortly and let you know what I find. Thanks, -Matt Russell Butek To: Matthew Duftler/Watson/IBM@IBMUS 01/22/2002 03:06 cc: [EMAIL PROTECTED] PM From: Russell Butek/Austin/IBM@IBMUS Subject: WSDL4J bug 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: , . 2. A similar problem is a WSDL with stanzas in the normal order, but with overloaded operations; in other words, a portType and binding with two operations called "method" but with different input/output messages. A call to binding.getBindingOperations() returns the two BindingOperations. But a call to portType.getOperations() returns one of the operations twice and I never see the other one. Here's a wsdl and test for this variation: , . Russell Butek [EMAIL PROTECTED] #### duplicate.wsdl has been removed from this note on January 25 2002 by Matthew Duftler #### Test.java has been removed from this note on January 25 2002 by Matthew Duftler #### overload.wsdl has been removed from this note on January 25 2002 by Matthew Duftler #### ATTCQOWM has been removed from this note on January 25 2002 by Matthew Duftler
