DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15765>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15765 re: Incorrect error message thrown. Complaint of lack of method syncronization [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2003-01-03 14:31 ------- Hi James: I had a different problem with your WSDL - since the namespace was "urn:AxisLMSServer", it created all the files in package "AxisLMSServer". As there was also a class "AxisLMSServer" in that package, any time there was a fully-qualified reference to another class like "AxisLMSServer.AxisLMSServerService", the compiler couldn't seem to figure out whether the AxisLMSServer before the dot was referring to the class or the package. So I couldn't compile the code (I'm surprised it worked for you!), let alone get to the point of deploying. I changed the namespace to urn:myNamespace, and attached my new WSDL here. That WSDL2Java-ed just fine, and I was able to deploy the service and get the ?WSDL with no problems. So I'm going to close this bug with a "worksforme" for now, and open a new one about the name clash problems.
