You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Vincent (JIRA)" <ji...@apache.org> on 2008/05/05 05:44:55 UTC
[jira] Created: (AXIS2-3778) Axis2 1.3 can work, but fails in Axis2
1.4
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
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 find the wsdls from the website: http://www.parlay.org/imwp/idms/popups/pop_download.asp?ContentID=11411
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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels resolved AXIS2-3778.
---------------------------------
Resolution: Fixed
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.5
>
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent Dou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Dou updated AXIS2-3778:
-------------------------------
Description:
It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
For example:
The wsdls are from ETSI/3GP ParlayX Web service specification.
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
see the attached wsdls , which are from the 3GPP site:
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 :
<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 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>
was:
It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
For example:
The wsdls are from ETSI/3GP ParlayX Web service specification.
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 :
<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 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: wsdl
> Affects Versions: 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-3778) For the case of multiple
WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594135#action_12594135 ]
douster edited comment on AXIS2-3778 at 5/4/08 9:27 PM:
--------------------------------------------------------
Attached is the debug log file for the makeCall Request.
was (Author: douster):
Attached the debug log file for the makeCall Request.
> 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: axis2.log, 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case multiple WSDLs and XSDs
for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Attachment: ThirdPartyCallService.aar
Attach the Axis2 v1.4 service package : ThirdPartyCallService.aar
The correct response should be Exception "Please implement ThirdPartyCallServiceSkeleton#makeCall"
But now the response is
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>unknown</faultstring>
<detail/>
</soapenv:Fault>
> For the case 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/">
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) Axis2 1.3 can work, but fails in Axis2
1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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
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>
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 find the wsdls from the website: http://www.parlay.org/imwp/idms/popups/pop_download.asp?ContentID=11411
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>
> 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
>
> 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
> 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent Dou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Dou updated AXIS2-3778:
-------------------------------
Attachment: WSDLs.zip
See the attached WSDLs.zip for wsdls
> 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: wsdl
> Affects Versions: 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case multiple WSDLs and XSDs
for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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
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>
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
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 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
>
> 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
> 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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 :
<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 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>
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/" 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>
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-3778:
----------------------------------------
Assignee: Amila Chinthaka Suriarachchi
> 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: wsdl
> Affects Versions: 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent Dou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656529#action_12656529 ]
Vincent Dou commented on AXIS2-3778:
------------------------------------
Hi Daniels,
Okey. You can close it. Thanks.
Vincent
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.5
>
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Attachment: axis2.log
Attached the debug log file for the makeCall Request.
> 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: axis2.log, 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-3778) For the case of multiple
WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594134#action_12594134 ]
douster edited comment on AXIS2-3778 at 5/4/08 9:27 PM:
--------------------------------------------------------
Attached ThirdPartyCallService.aar is the Axis2 v1.4 service package :
The correct response should be Exception "Please implement ThirdPartyCallServiceSkeleton#makeCall"
But now the response is
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>unknown</faultstring>
<detail/>
</soapenv:Fault>
was (Author: douster):
Attach the Axis2 v1.4 service package : ThirdPartyCallService.aar
The correct response should be Exception "Please implement ThirdPartyCallServiceSkeleton#makeCall"
But now the response is
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>unknown</faultstring>
<detail/>
</soapenv:Fault>
> 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: axis2.log, 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656528#action_12656528 ]
Glen Daniels commented on AXIS2-3778:
-------------------------------------
Hi Vincent,
I just tried downloading your WSDLs, generating the service per your command line above (except I defaulted to ADB rather than explicitly specifying it). I then deployed the service and tested it with the current Axis2 trunk. I got the expected "Please implement org.csapi.www.wsdl.parlayx.third_party_call.v2_3.service.ThirdPartyCallServiceSkeleton#makeCall" fault.
So... I'm going to mark this as fixed. If you disagree, please feel free to reopen it. You can find a nightly build to test with at http://builder.wso2.org/browse/AXIS2-NIGHTLY/ - I'm just rebuilding that now after Keith's build fix, so there should be a fresh one available in about 45m. You can also use the previous successful one at http://builder.wso2.org/browse/AXIS2-NIGHTLY-226.
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.5
>
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Component/s: (was: kernel)
wsdl
Priority: Critical (was: Blocker)
> 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: wsdl
> Affects Versions: 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent
> Priority: Critical
> Attachments: axis2.log, ThirdPartyCallService.aar
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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 this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
For example:
The wsdls are from ETSI/3GP ParlayX Web service specification.
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 :
<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 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>
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 :
<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 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>
Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4 (was: Windows XP
Axis2 1.3 and Axis2 1.4)
> 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 , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2-3778) For the case of multiple
WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594135#action_12594135 ]
douster edited comment on AXIS2-3778 at 5/4/08 9:28 PM:
--------------------------------------------------------
Attached axis2.log is the debug log file for the makeCall Request.
was (Author: douster):
Attached is the debug log file for the makeCall Request.
> 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: axis2.log, 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Priority: Blocker (was: Critical)
> 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: wsdl
> Affects Versions: 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Summary: For the case of multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4 (was: For the case multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4)
> 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/">
> <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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels updated AXIS2-3778:
--------------------------------
Fix Version/s: 1.5
Targeting this for 1.5
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.5
>
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case multiple WSDLs and XSDs
for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent updated AXIS2-3778:
---------------------------
Summary: For the case multiple WSDLs and XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4 (was: Axis2 1.3 can work, but fails in Axis2 1.4)
> For the case 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
>
> 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
> 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645197#action_12645197 ]
Amila Chinthaka Suriarachchi commented on AXIS2-3778:
-----------------------------------------------------
try to create a proper exception and throw
eg.
org.csapi.www.schema.parlayx.common.v2_1.ServiceException serviceE = new org.csapi.www.schema.parlayx.common.v2_1.ServiceException();
serviceE.setMessageId("msgID");
serviceE.setMessageId("text");
serviceE.setVariables(new String[]{"test", "test1"});
ServiceExceptionE serviceExceptionE = new ServiceExceptionE();
serviceExceptionE.setServiceException(serviceE);
ServiceException serviceException = new ServiceException();
serviceException.setFaultMessage(serviceExceptionE);
throw serviceException;
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Fix For: 1.5
>
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case of multiple WSDLs and
XSDs for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent Dou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Dou updated AXIS2-3778:
-------------------------------
Affects Version/s: 1.4.1
> 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: wsdl
> Affects Versions: 1.4.1, 1.4
> Environment: Windows XP , JDK1.5.0_14 , Axis2 1.3 and Axis2 1.4
> Reporter: Vincent Dou
> Assignee: Amila Chinthaka Suriarachchi
> Priority: Blocker
> Attachments: axis2.log, ThirdPartyCallService.aar, WSDLs.zip
>
>
> It's easy to reproduce this issue. The case is that there are multiple WSDLs and XSDs for one service. It works fine with Axis2 1.3. But fail for new release Axis2 1.4.
> For example:
> The wsdls are from ETSI/3GP ParlayX Web service specification.
> 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
> see the attached wsdls , which are from the 3GPP site:
> 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 :
> <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 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3778) For the case multiple WSDLs and XSDs
for one service, Axis2 1.3 can work, but fails in Axis2 1.4
Posted by "Vincent (JIRA)" <ji...@apache.org>.
[ 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/">
<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
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 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
>
> 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>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org