[ http://issues.apache.org/jira/browse/AXIS-2355?page=comments#action_12361367 ]
Steve Loughran commented on AXIS-2355: -------------------------------------- This is why it is so dangerous to use any implementation-driven WSDL creation process for your public interface: any change in the implementation can break that interface, and you end up living in fear of all tool upgrades. The best workaround is -save that original WSDL -make that the public interface, and stop having axis create WSDL from your implementation -edit server-config.wsdd to return your saved WSDL from a resource in the webapp -use wsdl2java server-side as well as client-side, and bind the generated classes to your application Whenever axis gets updated you may have to regenerate and edit your generated server-side classes, but it guarantees the interface is stable. the other option (which is too late this time round, but maybe next time...), is to write your own WSDL from the outset. > java2wsdl produces different wsdl in 1.2.1 than in 1.1 > ------------------------------------------------------ > > Key: AXIS-2355 > URL: http://issues.apache.org/jira/browse/AXIS-2355 > Project: Apache Axis > Type: Bug > Components: WSDL processing > Versions: 1.2.1 > Reporter: Parag Bhogte > > I am excited to move to new version, mainly for JDK 5 compatibility. This > allows us to use new technologies such as EJB 3.0. However, as we are > releasing new versions of our software, we do not want to break existing > clients who are used to the old style wsdl. If we made major changes to the > wsdl, they will have to make major changes to the client which may or may not > be using Java & Axis. This is not good for business. > Looks like when I use java2wsdl in 1.2.1 it gives me different result than > 1.1. Is there any option to generate old-style wsdl? I am already using -T > 1.1 for wsdl generation. > The changes: > 1. There is new attribute in the header: > xmlns:apachesoap="http://xml.apache.org/xml-soap"; > 2. Instead of > <element maxOccurs="unbounded" name="displayAttributes" nillable="true" > type="tns1:NamedValue"/> > I get > <element name="displayAttributes" nillable="true" > type="impl:ArrayOf_tns1_NamedValue"/> > <schema xmlns="http://www.w3.org/2001/XMLSchema"; > targetNamespace="http://www.xxx.com/sms/api/r06_02/XXXService";> > <import namespace="http://www.xxx.com/sms/api/r06_02/model"/> > <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/> > <complexType name="ArrayOf_tns1_NamedValue"> > <complexContent> > <restriction base="soapenc:Array"> > <attribute ref="soapenc:arrayType" wsdl:arrayType="tns1:NamedValue[]"/> > </restriction> > </complexContent> > </complexType> > 3. Instead of > <wsdl:fault name="APINetworkException"> > <wsdlsoap:fault > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > namespace="http://www.xxx.com/sms/api/r06_02/XXXService"; use="encoded"/> > </wsdl:fault> > I get > <wsdl:fault name="APINetworkException"> > <wsdlsoap:fault > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; > name="APINetworkException" > namespace="http://www.xxx.com/sms/api/r06_02/XXXService"; use="encoded"/> > </wsdl:fault> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
