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:48:55 UTC
[jira] Updated: (AXIS2-3778) Axis2 1.3 can work, but fails in Axis2
1.4
[ 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