Valid SOAP response

Hi All,
I have a problem with a webservice response. I need to invoke a webservice (binary implementation is different) that is located in two seperate servers (binary implementation is different). Each webservice has the same interface for both the request and the response. My cliente (calling code) is using the Java API for XML-based RPC (JAX-RPC) and is implemented using weblogic server 7.0 to invoke the two web services. I can invoke correctly one of the web services but I get an error with the other one.
I have seen in other forums that weblogic requires a property passed in when you start weblogic called:
weblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1
where I pass in like
'Dweblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1'
but this has not solved the problem.
Questions:
1: Does the WSDL have to be the same for the two web services ?
2: Is it a problem with the response (XML) or a communication error ?
Thanking you in advance,
Nacho
PD: The error I get is:
com.amena.sgp.funcionalidades.incidencias.excepciones.ErrorEnvioEstado: Error reading the response from: https://ws/webservice/gi. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:316)
at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirPendiente(IncidenciaEmisor.java:466)
at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirIncidencia(IncidenciaEmisor.java:129)
at com.amena.sgp.funcionalidades.incidencias.FactoriaIncidencias.obtenerIncidencia(FactoriaIncidencias.java:117)
at com.amena.sgp.factoria.comandos.incidencias.CmdCrearIncidenciaEmisor.ejecutarComando(CmdCrearIncidenciaEmisor.java:169)
at com.amena.sgp.servlets.Controlador.doGet(Controlador.java:147)
at com.amena.sgp.servlets.Controlador.doPost(Controlador.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
and :
unknown attr1.3.6.1.4.1.311.17.1

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
<m:gi-apertura xmlns:m="urn:pm_gi_interfaz_soap2"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<cod-usuario xsi:type="xsd:string"></cod-usuario>
<tex-password xsi:type="xsd:string"></tex-password>
<cod-usuactuacion xsi:type="xsd:string">Administrador</cod-usuactuacion>
<cod-incidencia xsi:type="xsd:string">AME-6002-000000061</cod-incidencia>
<tip-asociado xsi:type="xsd:string">M</tip-asociado>
<tex-asociado xsi:nil="true">
</tex-asociado>
<fec-actuacion xsi:type="xsd:string">29/08/2005 14:58:43</fec-actuacion>
<lst-msisdn>
<item>
</item>
</lst-msisdn>
<tex-incidencia xsi:type="xsd:string">Prueba de sistemas.</tex-incidencia>
</m:gi-apertura>
</env:Body>
</env:Envelope>Handshake finished!
CipherSuite:SSL_RSA_WITH_RC4_128_MD5
SessionId [Session-2, SSL_RSA_WITH_RC4_128_MD5]
PeerHost www.portabilidad.vodafone.es
java.io.CharConversionException: Illegal ASCII character, 0xf3
at weblogic.xml.babel.reader.XmlReader$AsciiReader.read(XmlReader.java:824)
at weblogic.xml.babel.scanner.ScannerState.read(ScannerState.java:382)
at weblogic.xml.babel.scanner.ScannerState.expect(ScannerState.java:235)
at weblogic.xml.babel.scanner.CloseTag.read(CloseTag.java:21)
at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:226)
at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
at weblogic.xml.babel.baseparser.BaseParser.prime(BaseParser.java:243)
at weblogic.xml.babel.baseparser.BaseParser.initScanner(BaseParser.java:107)
at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:222)
at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:101)
at weblogic.xml.babel.parsers.XMLInputStreamParser.<init>(XMLInputStreamParser.java:35)
at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:64)
at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:48)
at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:66)
at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:53)
at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:95)
at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:128)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:165)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
amount read:0inputBufferSize512overflow256
Error at line:1 col:562 Got character[0] expected a valid XML character
at weblogic.xml.babel.scanner.ScannerState.checkedRead(ScannerState.java:594)
at weblogic.xml.babel.scanner.CharData.read(CharData.java:65)
at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:265)
at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
at weblogic.xml.babel.baseparser.BaseParser.accept(BaseParser.java:451)
at weblogic.xml.babel.baseparser.StartElement.parse(StartElement.java:77)
at weblogic.xml.babel.baseparser.BaseParser.parseElement(BaseParser.java:381)
at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:278)
at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:120)
at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
--------------- nested within: ------------------
weblogic.xml.stream.XMLStreamException: Got character[0] expected a valid XML character - with nested exception:
[Error at line:1 col:562 Got character[0] expected a valid XML character]
at weblogic.xml.babel.adapters.XMLInputStreamElementFactory.create(XMLInputStreamElementFactory.java:106)
at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:123)
at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
<Aug 29, 2005 2:58:48 PM MEST> <Info> <webservice> <220025> <Handler weblogic.webservice.core.handler.ClientHandler threw an exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: java.io.IOException: Error reading the response from: https://www.xxx.xxxx. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Error reading the response from: https://xxx.xxx.xxx/wwww. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope></faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: https://www.xxx.xxxe. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:189)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>

I'm having the same problem. We were calling the service via weblogic.jws.proxies. , after moving end point to another host in other lan (tunneled to old end point )
After this we can't invoke old methods all we got is this exception
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope></faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:195)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:456)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:377)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:244)
at weblogic.jws.proxies.FetchAtmosferaRejectableGroups_PortType_Stub.fetchAtmosferaRejectableGroups(FetchAtmosferaRejectableGroups_PortType_Stub.java:33)
at pl.era.prime.integration.client.AtmPCHS2PrimeBean.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeBean.java:167)
at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeSession_lm80md_EOImpl.java:46)
at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:455)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:396)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:726)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:391)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
I suppose the problem is in setting end point for back response, has any one similar problem ??

Similar Messages

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Weblogic throwing "null SOAP element Exception" in multi-part SOAP response

Hi All,
I'm using weblogic 10. My application is a webservice client generated using '*clientgen*', which is running on weblogic, and
is invoking a remotely hosted webservice ( Remotely hoseted webservice may not be running on weblogic).
I've the wsdl file of remotely hosted webservice.
Now the problem is with WSDL file (I suppose), have a look at this.
*<message name="m1">*
*<part name="body" element="tns:GetCompanyInfo"/>*
*</message>*
*<message name="m2">*
*<part name="body" element="tns:GetCompanyInfoResult"/>*
*<part name="docs" type="xsd:AnyComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*<part name="logo" type="xsd:AnyOtherComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*</message>*
<portType name="pt1">
<operation name="GetCompanyInfo">
<input message="m1"/>
*<output message="m2"/> -----> multi part message.*
</operation>
</portType>
Now here is sample message for the request(I've composed this message for this question):
<soap:Envelope> MESSAGE1
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs> Assume no data for 'logo', so it's not returned. Since all its elements can be nillable.
<tns:m2>
</soap:body>
</soap:Envelope>
First of all, is this SOAP response is valid? I'm not sure about *'message' and 'parts' in SOAP*, but according to XML schema standards it's invalid.
Because, according to *'message' m2, 'logo' is missing*, eventhough all it's elements are nillable in such case there should be *<logo/>* at the end.
I mean valid message should be like below
<soap:Envelope> '*MESSAGE2*'
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs>
*<tns:logo/> ------------------> here is the change compared to above message. empty element.*
<tns:m2>
</soap:body>
</soap:Envelope>
Now the concerns are :
(1) Which is a valid response? Message1 or Message2
(2) If message1 is valid then why is weblogic throwing an exception 'null SOAP element', I suppose this is due to missing 'logo' element.
(To confirm this I've used tcpmonitor and found message1 as response but weblogic is still throwing 'null SOAP Element' exception,
which confirms it needs 'logo' as well, I suppose <logo/> at least). Is there any workaround for this in weblogic for multi-part messages?
(3) If message1 is invalid according to SOAP standards then You've answered my question. ---> I need to talk to the webservice provider in this case.....
Thanks in advance...

Message 1 is not Basic Profile 1.1 compliant. It is specified by BP1.1 in section 4.4.1(http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_and_Parts) that when a wsdl:part element is defined using the type attribute, the serialization of that part in a message is equivalent to an implicit (XML Schema) qualification of a minOccurs attribute with the value "1", a maxOccurs attribute with the value "1" and a nillable attribute with the value "false".

Error at SOAP response channel

Dear All,
I have created a synchronous PROXY to SOAP scenario. But I am getting the following error in the receiver SOAP Adapter.
Message processing failed. Cause:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP:
response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION -
soap fault: System.Web.Services.Protocols.SoapException: Server was unable to
process request. ---> System.NullReferenceException: Object reference not set
to an instance of an object.
--- End of inner exception stack trace ---
Please suggest what may be the reason for it.
Thanks and Regards,
Rana Brata De
SAP PI Consultant

Hi,
We have faced similar problem in production some time back .
At target system end web service validates the payload below inserting into back end system (d/b).If the validation fails then it throws the error to PI system .
For us the backend system notified that there end front end service validation failed due to data issue and thrown exception to PI.
Share the payload to target system folks and ask them to check ,they will have test suite to test it from there end . If not share the time at which you received error,they will check there logs and update you on the cause .
Regards
Venkat

Raised warnings in SOAP response - where are they?

I am calling a rulebase deployed on a determinations-server using the generic SOAP web services.
Using Java and JAX-WS I can build a valid request, call the service, and receive a response which I can interpret - and I can handle the SOAPFaultException thrown when an error is raised by the rulebase.
So far so good - however, when my rulebase raises a warning - how is that supposed to be reflected in the SOAP response?
As far as I can see - there is no trace of any raised warnings in the response - and I have tried calling with both "value-only" and "decision-report" outcome style.
Any pointers to documentation or examples will be greatly appreciated.
Thanks in advance,
- Tom

I found the answer myself: Adding a <show-events>true</show-events> to the config-part of the request did the trick.
The response now contains an <events> section listing the raised warning from the rulebase.
I guess sometimes the answer is right in front of you - I hope somebody else can benefit from this information.
- Tom

Prefix namespace OSB, SOAP response

Hi!
I'm doing a web service in OSB 11g.
An application is parsing the SOAP response after calling my WS, and they are expecting that my SOAP response have hardcode prefixes.
My SOAP response is like this:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
XXXX
</soapenv:Body>
</soapenv:Envelope>
They want another prefix (soap instead of env or other prefix). Something like this:
<soap:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
XXXX
</soap:Body>
</soap:Envelope>
Do you know how can I fix it? I know this is a problem of the application who is calling my WS, but if I can do this, I can solve them a problem.
Thanks!!

mybe the valid one is something like this,...please refer to the namespace,it sould be "xmlns:soap" than "xmlns:env" because you trying to use soap prefix .
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
XXXX
</soap:Body>
</soap:Envelope>
you can change the soap message in many way...for example you can use message processing actions such as 'replace action':
you can replace xpath . on variable $body with expression fn-bea:inlinedXML('<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
</soap:Body>
</soap:Envelope>')
hope it will helping you

Broken SOAP response

Hi all,
we develop a mobile application (.NET compact framework/ WinCE) making use of SOAP-Requests on SAP WebAS 6.20 patch level (PL) 37.
As we patched one of our systems to PL 42, the resulting SOAP response changed and can not interpreted correctly, causing in a managed error in Windows CE. Even if the web service on PL42 is consumed via Visual Studio the problem can not be corrected.
It seems that SAP has changed the namespace in the SOAP response. The WSDL, however, is unchanged.
Has anybody encountered similar problems or has some idea how to change the WSDL correctly?
Can a change in namespace be correct if the WSDL is not adjusted?
     Thanks
          Chris
Answer System PL37:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
          xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
   <Z_SZ_SEND_XML.Response
              xmlns="urn:sap-com:document:sap:rfc:functions">
     <XML>Hallo</XML>
   </Z_SZ_SEND_XML.Response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Answer System PL42:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
       xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
       xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" >
<SOAP-ENV:Body>
<rfc:Z_SZ_SEND_XML.Response
             xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
   <XML>Hallo</XML>
</rfc:Z_SZ_SEND_XML.Response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
WSDL(both)
<?xml version="1.0" encoding="utf-8"?>
<definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <s:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
      <s:element name="Z_SZ_SEND_XML">
        <s:complexType>
          <s:all />
        </s:complexType>
      </s:element>
      <s:element name="Z_SZ_SEND_XML.Response">
        <s:complexType>
          <s:all>
            <s:element name="XML" type="s:string" />
          </s:all>
        </s:complexType>
      </s:element>
    </s:schema>
</types>
<message name="Z_SZ_SEND_XMLInput">
    <part name="parameters" element="s0:Z_SZ_SEND_XML" />
</message>
<message name="Z_SZ_SEND_XMLOutput">
    <part name="parameters" element="s0:Z_SZ_SEND_XML.Response" />
</message>
<portType name="Z_SZ_SEND_XMLPortType">
    <operation name="Z_SZ_SEND_XML">
      <input message="s0:Z_SZ_SEND_XMLInput" />
      <output message="s0:Z_SZ_SEND_XMLOutput" />
    </operation>
</portType>
<binding name="Z_SZ_SEND_XMLBinding" type="s0:Z_SZ_SEND_XMLPortType">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <operation name="Z_SZ_SEND_XML">
      <soap:operation soapAction="http://www.sap.com/Z_SZ_SEND_XML" />
      <input>
        <soap:body use="literal" />
      </input>
      <output>
        <soap:body use="literal" />
      </output>
    </operation>
</binding>
<service name="Z_SZ_SEND_XMLService">
    <documentation>SAP Service Z_SZ_SEND_XML via SOAP</documentation>
    <port name="Z_SZ_SEND_XMLPortType" binding="s0:Z_SZ_SEND_XMLBinding">
      <soap:address location="http://brain05a.dsc-gmbh.de:8080/sap/bc/soap/rfc" />
    </port>
</service>
</definitions>

I agree that you should escalate your support request. However I do not think the problem is the namespace. Both messages seem consistent with the WSDL to me and the namespaces are the same. These two elements are equivelent:
<Z_SZ_SEND_XML.Response xmlns="urn:sap-com:document:sap:rfc:functions">
<rfc:Z_SZ_SEND_XML.Response xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
The difference between them is that one uses a namespace prefix (rfc in this example), the other does not. Both of these are valid for the WSDL you have provided. I would also say that using namespace prefixes as the PL42 system does is a better practice. So your problem is coming from something else I think. This could be an error with the xml parser if it can not handle namespace prefixes, but I'm fairly certain .NET Compact Framework can handle this.

Help: SOAP Response Fault when big string is returned

Hello all, I'm quite newbie on Flex and SOAP, so sorry if I'm making an obvious question
I have an application in Flex that consumes a webservice, and everything runs smoothly until I try to return a big string, which I find to be odd. In my tests, when the string is over 490 characters, I get the following message:
SOAP Response cannot be decoded. Raw response: faultCode="DecodingError" faultDetail="null"
I made a PHP client, just for testing, to consume the same webservice, that calls the same operation. But in this other client, I get no errors and the string is returned complete, with no problems.
Sorry for my english, and any help will be very appreciated! Thanks!
Here is my script:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
    <fx:Script>
        <![CDATA[
            import mx.collections.ArrayCollection;
            import mx.rpc.events.ResultEvent;
            [Bindable]private var testValue:String;
            protected function floappService_variableTestResultHandler(event:ResultEvent):void
                this.testValue = event.result as String;
        ]]>
    </fx:Script>
    <fx:Declarations>
        <s:WebService id="ws"
                      wsdl="mywebservice?wsdl"
            <s:operation name="variableTest"
                         result="floappService_variableTestResultHandler(event)"
                         fault="mx.controls.Alert.show(event.fault.faultString)"/>
        </s:WebService>
    </fx:Declarations>
    <mx:VBox width="100%" height="100%">
        <mx:Form width="100%" height="100%">
            <mx:FormItem>
                <mx:HBox>
                    <s:Button label="Variable Test" click="ws.variableTest()"/>
                    <mx:Text text="{testValue}"/>
                </mx:HBox>
            </mx:FormItem>
        </mx:Form>
    </mx:VBox>
</s:Application>

Here is the raw response in the case that I get no faults (string with 490 'A's)
HTTP/1.1 200 OK
Date: Tue, 21 Sep 2010 17:36:46 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.2
X-SOAP-Server: NuSOAP/0.7.3 (1.114)
Content-Length: 1027
Vary: Accept-Encoding
Connection: close
Content-Type: text/xml; charset=ISO-8859-1
ï»¿<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://fusionforge.inteligis.paqtc.org.br">
<SOAP-ENV:Body>
<ns1:variableTestResponse xmlns:ns1="http://fusionforge.inteligis.paqtc.org.br">
<myReturn xsi:type="xsd:string">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</myReturn>
</ns1:variableTestResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
And here is the case when I get the fault (string with 491 - or more - 'A's):
HTTP/1.1 200 OK
Date: Tue, 21 Sep 2010 17:40:40 GMT
Server: Apache/2.2.14 (Ubuntu)
X-Powered-By: PHP/5.3.2-1ubuntu4.2
X-SOAP-Server: NuSOAP/0.7.3 (1.114)
Content-Length: 1028
Vary: Accept-Encoding
Connection: close
Content-Type: text/xml; charset=ISO-8859-1
ï»¿<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://fusionforge.inteligis.paqtc.org.br">
<SOAP-ENV:Body>
<ns1:variableTestResponse xmlns:ns1="http://fusionforge.inteligis.paqtc.org.br">
<myReturn xsi:type="xsd:string">AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</myReturn>
</ns1:variableTestResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
I checked both XMLs "well-formedness" on W3 XML Validator (
http://www.w3schools.com/XML/xml_validator.asp), and got no errors.
The only difference between both responses is the Content-Length, so I'm guessing that it has something to do with it (don't have any idea of what/why)

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
<b>Scenario</b>: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
<b>SOAP</b> Receiver adaptor.
<b>Target URL</b> http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
<b>SOAP Action</b> http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the <b>sender</b> soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Hi All,
I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
Please suggest what will be possible way out to resolve this issue.
Thanks,
Priya Ranjan

Dear Priya
Have you configured Fault Message for this scenario.
This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
Sourabh

BPEL process to create a PDF and send it as attachment in SOAP response

We have a requirement to have a webservice created using BPEL, which can receive input from a client and create a PDF using the input and send the PDF as attachment in the SOAP response.
We have found the below link in Oracle docs and our basic understanding on the functionality given is that the MIMEService is being used to read a SOAP attachment from some other service and send it as an attachment in the SOAP response to the requester. As explained above, this doesn't completely satisfy our requirement.
http://docs.oracle.com/cd/E11036_01/integrate.1013/b28981/manipdoc.htm#BABCJIAH
Please suggest if there is any other approach that suites our requirement.
Thanks.

Hi,
I have a Weblogic webservice which returns me a PDF attachment as resposne ( here I have MIME related stuff).I need to get attachment as bpel response.
I have created a BPEL process to invoke the weblogic webservice. I have explictly added the MIME part in bpel.wsdl same as weblogic webservice wsdl.
I tried to assign the response variable( of type base64binary) of bpel.wsdl and my webservice .wsdl . I am getting some error with no attachment.
Below is my xsd used in BPEL.wsdl*
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
     elementFormDefault="qualified"
     targetNamespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
     xmlns="http://www.w3.org/2001/XMLSchema">
     <complexType name="process">
               <sequence>
                    <element name="input" type="string"/>
               </sequence>
     </complexType>
     <complexType name="processResponse">
               <sequence>
                    <element name="result" type="string"/>
               </sequence>
     </complexType>
<complexType name="GetAttachmentPDF">
<sequence>
<element minOccurs="0" name="Pdf" nillable="false" type="base64Binary"/>
</sequence>
</complexType>
</schema>
Below is my BPEL.wsdl*
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="BPELProcess1"
targetNamespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">

<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
schemaLocation="xsd/BPELProcess1.xsd"/>
</schema>
</wsdl:types>

<wsdl:message name="BPELProcess1RequestMessage">
<wsdl:part name="payload" type="client:process"/>
</wsdl:message>
<wsdl:message name="BPELProcess1ResponseMessage">
<wsdl:part name="payload" type="client:processResponse"/>
<wsdl:part name="attachment" type="client:GetAttachmentPDF"/>
</wsdl:message>


<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage"/>
<wsdl:output message="client:BPELProcess1ResponseMessage"/>
</wsdl:operation>
</wsdl:portType>

<plnk:partnerLinkType name="BPELProcess1">
<plnk:role name="BPELProcess1Provider">
<plnk:portType name="client:BPELProcess1"/>
</plnk:role>
</plnk:partnerLinkType>
<wsdl:binding name="BPELProcess1SOAP11Binding" type="client:BPELProcess1">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="process">
<soap:operation style="rpc"
soapAction="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1/process"/>
<wsdl:input>
<soap:body use="literal"
namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"/>
</wsdl:input>
<wsdl:output>
<mime:multipartRelated>
<mime:part>
<soap:body use="literal"
namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"/>
</mime:part>
<mime:part>
<mime:content part="attachment" type="application/pdf"/>
</mime:part>
</mime:multipartRelated>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
Below is my WL WS WSDL*
<?xml version="1.0" encoding="UTF-8"?>
<WL5G3N0:definitions
name="NewWSDLFile"
targetNamespace="http://www.example.org/NewWSDLFile/"
xmlns:WL5G3N5="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:WL5G3N4="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:WL5G3N3="http://www.example.org/NewWSDLFile/"
xmlns:WL5G3N2="java:com.rogers.service"
xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/"
xmlns:WL5G3N1="http://www.w3.org/2001/XMLSchema"
>
<WL5G3N0:types>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.rogers.service"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="java:com.rogers.service"
xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://www.w3.org/2001/XMLSchema"
xmlns:s2="java:com.rogers.service" xmlns:s3="http://www.example.org/NewWSDLFile/"
xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s5="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/NewWSDLFile/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="GetAttachmentPDF">
<xsd:sequence>
<xsd:element minOccurs="0" name="Pdf" nillable="false" type="xs:base64Binary"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GetAttachmentResult">
<xsd:sequence>
<xsd:element minOccurs="1" name="Message" nillable="true" type="xs:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</WL5G3N0:types>
<WL5G3N0:message name="NewOperationRequest">
<WL5G3N0:part name="GetAttachment" type="WL5G3N1:string"/>
</WL5G3N0:message>
<WL5G3N0:message name="NewOperationResponse">
<WL5G3N0:part name="NewOperationResponse" type="WL5G3N2:GetAttachmentResult"/>
<WL5G3N0:part name="attachment" type="WL5G3N2:GetAttachmentPDF"/>
</WL5G3N0:message>
<WL5G3N0:portType name="NewWSDLFile">
<WL5G3N0:operation name="NewOperation">
<WL5G3N0:input message="WL5G3N3:NewOperationRequest"/>
<WL5G3N0:output message="WL5G3N3:NewOperationResponse"/>
</WL5G3N0:operation>
</WL5G3N0:portType>
<WL5G3N0:binding name="NewWSDLFileSOAP" type="WL5G3N3:NewWSDLFile">
<WL5G3N4:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N0:operation name="NewOperation">
<WL5G3N4:operation soapAction="http://www.example.org/NewWSDLFile/NewOperation"/>
<WL5G3N0:input>
<WL5G3N4:body use="literal" namespace="http://www.example.org/NewWSDLFile/"/>
</WL5G3N0:input>
<WL5G3N0:output>
<WL5G3N5:multipartRelated>
<WL5G3N5:part>
<WL5G3N4:body use="literal" namespace="http://www.example.org/NewWSDLFile/"/>
</WL5G3N5:part>
<WL5G3N5:part>
<WL5G3N5:content part="attachment" type="application/pdf"/>
</WL5G3N5:part>
</WL5G3N5:multipartRelated>
</WL5G3N0:output>
</WL5G3N0:operation>
</WL5G3N0:binding>
<WL5G3N0:service name="NewWSDLFile">
<WL5G3N0:port name="NewWSDLFileSOAP" binding="WL5G3N3:NewWSDLFileSOAP">
<WL5G3N4:address location="http://localhost:7001/something/NewWSDLFileImpl"/>
</WL5G3N0:port>
</WL5G3N0:service>
</WL5G3N0:definitions>
I refered the below link:
http://docs.oracle.com/cd/B14099_19/integrate.1012/b14448/manipdoc.htm.
4.16.1.1 WSDL File Contents
They are using ra:writeBinaryToFile() and ora:ReadBinaryFromFile(). I couldnt get a proper sample to understand the use of these functions.
Please advise.
Regards
Ipsita

Oracle ESB 10g : Blank namespace in the SOAP Response from DB adapter

Hi All,
I am currently working on a ESB project to route input XML file as a parameter to a DB Function.
This Function has a input parameter of type XMLTYPE and returns VARCHAR2 values.
I have configured the DB Adapter to invoke this function and return the result as a SOAP response.
The WSDL of DB adapter contains XML_DATA as input and XMLMAIN as the output result.
The ESB project works fine as expected. But in the result from DB adapter contains a blank namespace [xmlns=""] for the XMLMAIN element .
I hereby attach the output XML.
Please help how to remove this blank namespace from the output.
We are using SOA Suite 10g 10.1.3.5
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/XXWEB/XMLMISCRCPTINSERTPKG/XMLMAIN/">
<OutputParameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<XMLMAIN xmlns="">100</XMLMAIN>
</OutputParameters>
</env:Body>
</env:Envelope>
Thanks and Regards,
Justin Michael Raj

well..the problem is..the db adapter has it's own transaction..so the transactions fails or not.
you're just not capable of checking if the transaction went ok...and return 'process completed ok' or when the transaction failed for some reason return 'the process aborted'.
So you just need some extra steps for it to be able to return some response-message

SOAP Response XSLT Transformation Error

I am doing a webservice call and trying to transform the SOAP Response using XSLT.
I am getting the following error when the command CALL TRANSFORMATION Executes.
The element abap was expected for the XML-ABAP transformation
Please let me know if anyone ave received this error before and how did you solve it.
Regards
Sudhir Atluru

Hi Petra
for this Error com.sap.aii.af.ra.ms.api.ConfigException
check this Link
experts needed! com.sap.aii.af.ra.ms.api.ConfigException
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
also refer SAP Note 978606
Regards
Abhishek

How to deal with complex SOAP responses when calling web services ???

Hi all,
I have an issue when calling a web service that returns a complex
SOAP response message. With simple responses (e. g. array of strings) it
worked.
I created the PDF as an Interactive form with Livecycle Designer 8.2.
The Javascript looks like this:
var cURL = "http://blabla";
var cTestString = "too";
SOAP.wireDump=true;
var response = SOAP.request(
     cURL: cURL,
     oRequest: {
          "http://blabla.com/:complete" : {
          arg0: cTestString
          cAction: "http://bla.com:50000/"
var resp = response["http://blabla.com:serviceResponse"];
console.println("lenght:"+resp.length);
var myns = "http://blabla.com/namespace";
for (var nItem in resp.return)
console.println("" + nItem + " " + resp.return[nItem] );
     for (var ConceptView in resp.return[nItem])
       console.println(" "+resp.return[nItem].length);
       console.println(" "+ConceptView+" "+resp.return[nItem][ConceptView] );
       if (ConceptView == myns + ":Response")
          for (var item2 in resp.return[nItem][ConceptView]){
              console.println("    "+item2+" "+resp.return[nItem][ConceptView][item2] );
I call the service and when I realized that I do not find out the type of the object returned, I used the nested for-in-loops to iterate through it. But it seems that there is just one item in the Javascript object returned, although the SOAP message clearly shows that there are more than one item.
Can you help me?
One key problem when analyzing this issue is that I do not know at all
the Javascript type of response. We suspected it might be an array, but it is not
because the method .length returns "undefined". It would already be
helpful to know at least the type of this object and to know callable
methods and so on ...
Best regards
Christoph
P.S. As mentioned I used Livecycle Designer 8.2 and displayed and
debugged the document using Acrobat 9.

Christoph,
Firstly LiveCycle Designer 8.2 is still not supported to develop forms as per my knowledge. The latest version compatible for SAP Interactive Forms is ALD 8.0.
There is a difference between Acrobat based forms and LiveCycle forms and based on your coding it looks to me that you are trying to create a LiveCycle based form with coding of Acrobat which is not supported in LiveCycle Desginer, which is why you may be getting the error.
I hope that does not confuse you, so may check this [link|http://www.acrobatusers.com/articles/2006/08/designer_or_forms/index.php] for some clear information on what point I was trying to make.
Chintan

Valid SOAP response

Similar Messages

Maybe you are looking for