[ 
https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent updated AXIS2-3778:
---------------------------

    Description: 

It's easy to reproduce.  The case is that there are multiple WSDLs and XSDs for 
one service.

For example: 
The wsdls are from ETSI/3GP ParlayX Web service specification. 
It works fine with Axis2 1.3.  But fail in new release Axis2 1.4.

parlayx_third_party_call_types_2_3.xsd
parlayx_third_party_call_service_2_3.wsdl
parlayx_third_party_call_interface_2_3.wsdl
parlayx_common_faults_2_0.wsdl
parlayx_common_types_2_1.xsd

You can download the wsdls from : 
http://www.3gpp.org/ftp/specs/archive/29_series/29.199-02/29199-02-630.zip
http://www.3gpp.org/ftp/specs/archive/29_series/29.199-01/29199-01-630.zip

You can find the specification from the website:    
http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html

My command line to generate the java skeleton code: 
wsdl2java -uri ../wsdl/parlayx_third_party_call_service_2_3.wsdl -ss -sd -g -o 
../wsdl/gen_src/tpc -d adb
The service URL works fine after startup Axis2 1.4 simple server, the wsdl can 
be retrieved from 
           http://localhost:8080/axis2/services/ThirdPartyCallService?wsdl




When I send the request , such as Makecall , the client side shows result:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:loc="http://www.csapi.org/schema/parlayx/third_party_call/v2_3/local";>
   <soapenv:Header/>
   <soapenv:Body>
      <loc:makeCall>
         <loc:callingParty>tel:140111</loc:callingParty>
         <loc:calledParty>tel:1334455</loc:calledParty>      
      </loc:makeCall>
   </soapenv:Body>
</soapenv:Envelope>

The response :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server</faultcode>
         <faultstring>unknown</faultstring>
         <detail/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>



  was:

It's easy to reproduce.  The case is that there are multiple WSDLs and XSDs for 
one service.

For example: 
The wsdls are from ETSI/3GP ParlayX Web service specification. 
It works fine with Axis2 1.3.  But fail in new release Axis2 1.4.

parlayx_third_party_call_types_2_3.xsd
parlayx_third_party_call_service_2_3.wsdl
parlayx_third_party_call_interface_2_3.wsdl
parlayx_common_faults_2_0.wsdl
parlayx_common_types_2_1.xsd

You can download the wsdls from : 
http://www.3gpp.org/ftp/specs/archive/29_series/29.199-02/29199-02-630.zip
http://www.3gpp.org/ftp/specs/archive/29_series/29.199-01/29199-01-630.zip

You can find the specification from the website:    
http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html

My command line to generate the java skeleton code: 
wsdl2java -uri ../wsdl/parlayx_third_party_call_service_2_3.wsdl -ss -sd -g -o 
../wsdl/gen_src/tpc -d adb
The service URL works fine after startup Axis2 1.4 simple server, the wsdl can 
be retrieved from 
           http://localhost:8080/axis2/services/ThirdPartyCallService?wsdl

When I send the request , such as Makecall , the client side shows result:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server</faultcode>
         <faultstring>unknown</faultstring>
         <detail/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>




> For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, 
> but fails in Axis2 1.4
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3778
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3778
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.4
>         Environment: Windows XP
> Axis2 1.3 and Axis2 1.4
>            Reporter: Vincent
>            Priority: Blocker
>         Attachments: ThirdPartyCallService.aar
>
>
> It's easy to reproduce.  The case is that there are multiple WSDLs and XSDs 
> for one service.
> For example: 
> The wsdls are from ETSI/3GP ParlayX Web service specification. 
> It works fine with Axis2 1.3.  But fail in new release Axis2 1.4.
> parlayx_third_party_call_types_2_3.xsd
> parlayx_third_party_call_service_2_3.wsdl
> parlayx_third_party_call_interface_2_3.wsdl
> parlayx_common_faults_2_0.wsdl
> parlayx_common_types_2_1.xsd
> You can download the wsdls from : 
> http://www.3gpp.org/ftp/specs/archive/29_series/29.199-02/29199-02-630.zip
> http://www.3gpp.org/ftp/specs/archive/29_series/29.199-01/29199-01-630.zip
> You can find the specification from the website:    
> http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html
> My command line to generate the java skeleton code: 
> wsdl2java -uri ../wsdl/parlayx_third_party_call_service_2_3.wsdl -ss -sd -g 
> -o ../wsdl/gen_src/tpc -d adb
> The service URL works fine after startup Axis2 1.4 simple server, the wsdl 
> can be retrieved from 
>            http://localhost:8080/axis2/services/ThirdPartyCallService?wsdl
> When I send the request , such as Makecall , the client side shows result:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:loc="http://www.csapi.org/schema/parlayx/third_party_call/v2_3/local";>
>    <soapenv:Header/>
>    <soapenv:Body>
>       <loc:makeCall>
>          <loc:callingParty>tel:140111</loc:callingParty>
>          <loc:calledParty>tel:1334455</loc:calledParty>      
>       </loc:makeCall>
>    </soapenv:Body>
> </soapenv:Envelope>
> The response :
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
>    <soapenv:Body>
>       <soapenv:Fault>
>          <faultcode>soapenv:Server</faultcode>
>          <faultstring>unknown</faultstring>
>          <detail/>
>       </soapenv:Fault>
>    </soapenv:Body>
> </soapenv:Envelope>

-- 
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]

Reply via email to