Different Encoding from Axis 1.1 to Axis 1.2Alpha

[Canham Michael <Mi...@nrm.qld.gov.au>]

> To all,
> 
> I have successfully deployed Web Services using Axis 1.1.
> 
> However, the WSDL that was generated did not include the name in the wsdlsoap:fault.
> 
> Eg Axis 1.1 generated :
> 
>          <wsdl:fault name="NotFoundException">
>             <wsdlsoap:fault use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:WdSMIS"/>
>          </wsdl:fault>
> 
> 
> But other tools required :
> 
>          <wsdl:fault name="NotFoundException">
>             <wsdlsoap:fault name="NotFoundException" use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:WdSMIS"/>
>          </wsdl:fault>
> 
> 
> 
> I generated the WSDL using Axis1.2Alpha :
> 
> This fixed the name in the wsdlsoap:fault
> 
> However, when the wsdl was deployed to the Axis Server, the "published" WSDL used different encoding standard from the WSDL generated by Java2WSDL.
> 
> 
> ===========================================================================================================================
> WSDL as generated when services deployed :
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions targetNamespace="urn:WdSMIS" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:WdSMIS" xmlns:intf="urn:WdSMIS" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://access.common.wd" xmlns:tns2="http://www.w3.org/2003/05/soap-encoding" xmlns:tns3="http://parcel.in.wd" xmlns:tns4="http://exception.common.wd" xmlns:tns5="http://www.w3.org/1999/XMLSchema" xmlns:tns6="http://doc.common.wd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> 
> <schema targetNamespace="http://access.common.wd" xmlns="http://www.w3.org/2001/XMLSchema">
> <element name="TPassword" nillable="true" type="tns2:string"/>
> <element name="TSystem" nillable="true" type="tns2:string"/>
> <element name="TUserId" nillable="true" type="tns2:string"/>
> 
> ===========================================================================================================================
> WSDL as created by Java2WSDL 
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <wsdl:definitions targetNamespace="urn:WdSMIS" xmlns:tns3="http://parcel.in.wd" xmlns:impl="urn:WdSMIS" xmlns:intf="urn:WdSMIS" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns2="http://access.common.wd" xmlns:tns5="http://exception.common.wd" xmlns:tns4="http://doc.common.wd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
> 
> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://access.common.wd">
> <element name="TPassword" nillable="true" type="xsd:string"/>
> <element name="TSystem" nillable="true" type="xsd:string"/>
> <element name="TUserId" nillable="true" type="xsd:string"/>
> 
> 
> ===========================================================================================================================
> 
> 
> The client services that access the web services can not use the "new published" interface.
> 
> 
> 1) Why has the encoding changed ?
> 
> 2) Is there a way of specifying the same coding as the WSDL generated by Java2WSDL and supported by Axis 1.1 ?
> 
> 3) Does Axis1.2Beta behave in the same way as Axis1.2Alpha (in this regard) ?
> 
> 
> On a different note, 
> 
> 4) Can Axis1.1 and Axis1.2  reside on the Tomcat Server at the same time ?
> 
> 5) What determines which version of Axis that the tomcat Server uses ?
> 
> 
> 
> Many Thanks for your help,
> 
> Mike.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


************************************************************************
The information in this e-mail together with any attachments is
intended only for the person or entity to which it is addressed
and may contain confidential and/or privileged material.
Any form of review, disclosure, modification, distribution
and/or publication of this e-mail message is prohibited.  
If you have received this message in error, you are asked to
inform the sender as quickly as possible and delete this message
and any copies of this message from your computer and/or your
computer system network.  
************************************************************************