On 2/23/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Amila, Please check. -- dims ---------- Forwarded message ---------- From: Scott Kurz <[EMAIL PROTECTED]> Date: Feb 22, 2007 6:37 PM Subject: WSDL2Java - something in Axis2 to watch for To: [email protected] I was running WSDL2Java against a recent pull of Axis2 (like a week ago), newer than 1.1.1 and was failing running WSDL2Java. Just thought I'd get this down on paper for whenever we are ready to make this move... Axis2 introduced a 'codegen' boolean in their service builder building the AxisService from WSDL4J Definition and I couldn't get W2J to work unless I did: WSDL11ToAxisServiceBuilder builder = new WSDL11ToAxisServiceBuilder(...) builder.setCodegen(true); axisService = builder.populateService();
Axis2 had a codegen problem with the parameter order. In Axis2 1.1.1 the generated code had a different operations order than in the wsdl file itself. The reason for this was we kept axis operations in a Map in Axis2 service. So we introduce a new list to keep operations in order. As this list only needs in codegeneration time, the codegen boolean variable is used to have a track on it. So actually you have done the correct fix. please see the CodeGenerationEngine(CommandLineOptionParser parser) constructor in org.apache.axis2.wsdl.codegen.CodeGenerationEngine class. Amila. -- Amila Suriarachchi, WSO2 Inc.
