Bruno, Are you running the generation using the Ant script?
If so can you run with -debug .. Try to get me all the output, I'd like to see what it says... Thx! -----Original Message----- From: Bruno Harbulot [mailto:[EMAIL PROTECTED] Sent: Monday, May 08, 2006 9:28 AM To: wsrf-user@ws.apache.org Subject: Possible bugs in WSDL2Java? Hello, I'm getting some strange behaviour when I use the WSRF WSDL2Java. I'm using WSDL files adapted from the template (one of them is attached to this message). This file contains three custom operations: <operation name="markMilestone"> <input message="tns:markMilestoneRequestMsg" /> <output message="tns:markMilestoneResponseMsg" /> </operation> <operation name="start"> <input message="tns:startRequestMsg" /> <output message="tns:startResponseMsg" /> </operation> <operation name="end"> <input message="tns:endRequestMsg" /> <output message="tns:endResponseMsg" /> </operation> However, the Java file generated contains this: public interface TaskServicePortCustomOperationsPortType { public void markMilestone( uk.ac.esnw.task.MarkMilestoneRequestDocument requestDoc ) ; public void markMilestone( uk.ac.esnw.task.MarkMilestoneRequestDocument requestDoc ) ; } I get twice the same operation but the other two have mysteriously disappeared. Another problem I had was that I was using xmlns:types="http://www.esnw.ac.uk/TaskTypes"; and not xmlns:types="http://www.esnw.ac.uk/Task"; (similarly modified in the schemas so that it uses this: <xsd:schema targetNamespace="http://www.esnw.ac.uk/TaskTypes";> <xsd:import namespace="http://www.esnw.ac.uk/PulsarGrid"; /> <xsd:element name="markMilestoneRequest" type="pg:Milestone" /> </xsd:schema> This seemed to be a valid WSDL file. In this case, I get this: public interface TaskServicePortCustomOperationsPortType { public void end( requestDoc ) ; public void markMilestone(uk.ac.esnw.taskTypes.MarkMilestoneRequestDocument requestDoc ) ; } I had noticed in other cases as well that when the input message doesn't contain anything (e.g. <message name="startRequestMsg" />), there is still a parameter name without a type generated, where as "()" would be correct and appropriate. I can't find what's wrong with my WSDL file. Any suggestions? Regards, Bruno. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
