Hi guys,
Having an issue with composer…
The customer web service expects the data to be requested like this:
but composer is requesting the WS like this:
<arg0.input1></arg0.input1>
<arg0.input2></arg0.input2>
So far not been able to modify the way it is build…I see some JSon functions but don’t have time to investigate them and modify…also I think Composer should be able to do it so…I remember a similar issue on IRD and was able to manage it…
Some idea?
Thanks!
Hi Cav
In composer you can operate two web request blocks. One is standart HTTP web request to any supported web-service with out any data conversion. Second one used to invoke web-services and convert input/output data to JSON format.
I don’t try it before, but i belive that first one use native SOAP 1.x compatable request as WEB-service block in IRD. And it’s must be compatable with you customer web service. did you try it ?
WBR Timur
Ah! Will try it! I thought it was only for HTTP requests but worth to try 
Nop, didn’t work neither…
The issue is that the ASPX page by some reason adds the main node as a parent…I’m trying to see if there is any parameter on how to control this behavior but MS documentation is useless…
Hi Cav,
Can you post here WSDL of web service that you’re calling?
R.
Sure, here it is:
The one I’m now trying to test is dadosPessoa which is a complex of a complex…and there is the arg0
Thanks
<?xml version="1.0" encoding="UTF-8"?>-<wsdl:definitions xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/” xmlns:tns=“http://soap.soa.zerohora.ura.com.br/” xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/” xmlns:ns1=“http://cxf.apache.org/bindings/xformat” targetNamespace=“http://soap.soa.zerohora.ura.com.br/” name=“PersonServiceImplService”>
-wsdl:types<xs:schema xmlns:tns=“http://soap.soa.zerohora.ura.com.br/” targetNamespace=“http://soap.soa.zerohora.ura.com.br/” xmlns:xs=“http://www.w3.org/2001/XMLSchema” version=“1.0” elementFormDefault=“unqualified”>
<xs:element name=“dadosPessoa” type=“tns:dadosPessoa”/>
<xs:element name=“dadosPessoaResponse” type=“tns:dadosPessoaResponse”/>
<xs:element name=“prcDadosPessoaURA” type=“tns:prcDadosPessoaURA”/>
<xs:element name=“prcRegistraOcorrenciaURA” type=“tns:prcRegistraOcorrenciaURA”/>
<xs:element name=“registraOcorrencia” type=“tns:registraOcorrencia”/>
<xs:element name=“registraOcorrenciaResponse” type=“tns:registraOcorrenciaResponse”/><xs:complexType name=“dadosPessoa”>
xs:sequence
<xs:element name=“arg0” type=“tns:prcDadosPessoaURA” minOccurs=“0”/> </xs:sequence> </xs:complexType><xs:complexType name=“prcDadosPessoaURA”>
xs:sequence
<xs:element name=“codigoJornal” type=“xs:int”/>
<xs:element name=“numeroDocumento” type=“xs:string”/>
<xs:element name=“codigoPessoa” type=“xs:long” minOccurs=“0” nillable=“true”/>
<xs:element name=“nomePessoa” type=“xs:string” minOccurs=“0” nillable=“true”/>
<xs:element name=“boId” type=“xs:string” minOccurs=“0” nillable=“true”/>
<xs:element name=“codigoAssinatura” type=“xs:long” minOccurs=“0” nillable=“true”/>
<xs:element name=“result” type=“xs:int” minOccurs=“0” nillable=“true”/> </xs:sequence> </xs:complexType><xs:complexType name=“dadosPessoaResponse”>
xs:sequence
<xs:element name=“return” type=“tns:prcDadosPessoaURA” minOccurs=“0”/> </xs:sequence> </xs:complexType><xs:complexType name=“registraOcorrencia”>
xs:sequence
<xs:element name=“arg0” type=“tns:prcRegistraOcorrenciaURA” minOccurs=“0”/> </xs:sequence> </xs:complexType><xs:complexType name=“prcRegistraOcorrenciaURA”>
xs:sequence
<xs:element name=“codigoJornal” type=“xs:int”/>
<xs:element name=“codigoAssinatura” type=“xs:long”/>
<xs:element name=“codigoPessoa” type=“xs:long”/>
<xs:element name=“dataOcorrencia” type=“xs:date”/>
<xs:element name=“texto” type=“xs:string”/>
<xs:element name=“codigoMotivo” type=“xs:long”/>
<xs:element name=“result” type=“xs:int” minOccurs=“0” nillable=“true”/> </xs:sequence> </xs:complexType><xs:complexType name=“registraOcorrenciaResponse”>
xs:sequence
<xs:element name=“return” type=“tns:prcRegistraOcorrenciaURA” minOccurs=“0”/> </xs:sequence> </xs:complexType> </xs:schema> </wsdl:types>
-<wsdl:message name=“registraOcorrencia”> <wsdl:part name=“parameters” element=“tns:registraOcorrencia”> </wsdl:part> </wsdl:message>
-<wsdl:message name=“dadosPessoaResponse”> <wsdl:part name=“parameters” element=“tns:dadosPessoaResponse”> </wsdl:part> </wsdl:message>
-<wsdl:message name=“registraOcorrenciaResponse”> <wsdl:part name=“parameters” element=“tns:registraOcorrenciaResponse”> </wsdl:part> </wsdl:message>
-<wsdl:message name=“dadosPessoa”> <wsdl:part name=“parameters” element=“tns:dadosPessoa”> </wsdl:part> </wsdl:message>
-<wsdl:portType name=“PersonService”>
-<wsdl:operation name=“dadosPessoa”> <wsdl:input name=“dadosPessoa” message=“tns:dadosPessoa”> </wsdl:input> <wsdl:output name=“dadosPessoaResponse” message=“tns:dadosPessoaResponse”> </wsdl:output> </wsdl:operation>
-<wsdl:operation name=“registraOcorrencia”> <wsdl:input name=“registraOcorrencia” message=“tns:registraOcorrencia”> </wsdl:input> <wsdl:output name=“registraOcorrenciaResponse” message=“tns:registraOcorrenciaResponse”> </wsdl:output> </wsdl:operation> </wsdl:portType>
-<wsdl:binding name=“PersonServiceImplServiceSoapBinding” type=“tns:PersonService”> <soap:binding transport=“http://schemas.xmlsoap.org/soap/http” style=“document”/> +<wsdl:operation name=“dadosPessoa”>–
-<wsdl:operation name=“registraOcorrencia”> <soap:operation style=“document” soapAction=“”/>
-<wsdl:input name=“registraOcorrencia”> <soap:body use=“literal”/> </wsdl:input>
-<wsdl:output name=“registraOcorrenciaResponse”> <soap:body use=“literal”/> </wsdl:output> </wsdl:operation> </wsdl:binding>
-<wsdl:service name=“PersonServiceImplService”>
-<wsdl:port name=“PersonServiceImplPort” binding=“tns:PersonServiceImplServiceSoapBinding”> <soap:address location=“http://192.168.50.232:8081/ws_ura_hlg/personService”/> </wsdl:port> </wsdl:service> </wsdl:definitions>
Can You use backend block? It will create aspx/jsp page where You can invoke any code You wish - in Your case stub class for handling this comples WS and return result after processing in json format back to vxml.
Cav,
I did quick test using provided WSDL and Composer generates correct SOAP message IMHO
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<p:dadosPessoa xmlns:p="http://soap.soa.zerohora.ura.com.br/"><arg0><codigoJornal/><numeroDocumento/><codigoPessoa/><nomePessoa/><boId/><codigoAssinatura/><result/></arg0></p:dadosPessoa>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
R.
Which version of Composer René?? Can you share a screenshot?? I tried several ways and not single one worked for me…
The backend yes, is another idea, but I need to show the customer this working without many external tools and show him how GVP can work with them without 3rd party software…aka, fucked…
ah! forgot to mention that I’m using a Net project…don’t if the Net libraries are the responsible ones in any case…
Hi Cav,
I did my test using Java Composer project. I repeated the test with .NET Composer project and got same result as you >:(. It means there exists discrepancy in how Java and .NET web service blocks handle input parameters. It is evident that .NET web service block doesn’t support parameters of xs:complexType/xs:sequence type even Release Notes saying that such parameters are supported.
You have several options how to ‘fix’ the issue:
1/ Switch to Java Composer project
2/ Modify web service interface so complex type/sequences are not used
3/ Use Backend block and write you own web service call implementation
4/ Modify Composer’s getWebServiceData.aspx page to support complex types/sequences
5/ Raise ticket with Genesys Support to get a fix
R.
Yup, I have all this options on road right now
but will take a while before they will answer something goodThanks a lot René!
Just to update guys, Genesys guys confirmed that it is a bug…and solution on February…damn it…