On Thu, Jul 20, 2017 at 1:44 PM, Jon Wong <jw...@accu-time.com> wrote: > Dear all, > > I am currently trying to upgrade an existing Web Service that was written in > Axis 1.4 to Axis2 1.7.5. I have taken the existing Axis 1.4 WSDL and used > the Axis2 1.7.5 Wsdl2Java tool to create the Java files with the following > command: > > ./wsdl2java.sh -uri [my wsdl location].wsdl -d adb -wv 1.1 -ss -sd -ssi > > > After running the command, some of the generated classes have a capital "E" > appended to them such as responseE.java. Is this a known Axis2 bug or an > issue with my Wsdl or is this expected behavior? >
Don't recall ever seeing that issue. I'd suspect the wsdl. BTW, there is a migration guide from axis1 to axis2: https://axis.apache.org/axis2/java/core/docs/migration.html > Also is deploying an Axis2 service in an .aar file necessary? Could one just > use a .war file instead? > AFAIK the aar is required and it needs to be inside the WAR, though you can expand it as a directory under, for example, WEB-INF/services/myAARDir . --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
