The change in Java2WSDL that is wreaking havoc is that Java2WSDL is now picking up non-public methods on the target class, by default.
Even if I specify the list of methods to use on the command line, if I have an overloaded method, one private and one public they BOTH get picked up. Then we run into the WSDL2Java overloaded method problem. Is this something we want? Exposing non-public methods as web services? - Bob -- SynXis Corporation | [EMAIL PROTECTED] | Obstacles are those frightful 1610 Wynkoop, Suite 400 | Ph: (303)595-2511 | things you see when you take your Denver, CO 80202 | Fax:(303)534-4257 | eyes off your goal. -Henry Ford
