[ https://issues.apache.org/jira/browse/AXIS2-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-737. ------------------------------------------------ Resolution: Fixed fixed the issue with the rev 506986. set the operation list in axis service and get it when retriving services > WSDL2Java reverses the order of the Operations listed in the WSDL. > ------------------------------------------------------------------ > > Key: AXIS2-737 > URL: https://issues.apache.org/jira/browse/AXIS2-737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen > Reporter: Davanum Srinivas > Assigned To: Amila Chinthaka Suriarachchi > > Original email: > http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200605.mbox/[EMAIL > PROTECTED] > 11. Annoyance: WSDL2Java reverses the order of the Operations listed in > the WSDL. > In my WSDL the Operations are listed in this order: getAppReleases, > getAppReleasesSorted. Yet, in all the artifacts created by WSDL2Java, the > operations, their messages, their associated methods, their entries in the > services.xml file, their order in the generated WSDL file and their order > in the axis2-admin/listServices page is reversed from what exists in my > WSDL file. I prefer to have messages and operations in WSDLs and > attributes and methods in Classes in alphabetical order. I prefer that my > tools maintain the order that I have established. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]