| Author |
Message
|
| mpaucara |
 Posted: Thu Apr 16, 2009 1:27 pm Post subject: Help Using Node Soap Async Request |
 |
|
Newbie
Joined: 23 Mar 2009
Posts: 3
|
Hola a todos, disculpen que hable en español pero necesito esta ayuda urgente.
Tengo un problema al usar el nodo Soap Async Request que consume un web service hecho en .NET(que por cierto me indican que soporta WS-Addressing). El asunto esta en que no puedo obtener respuesta del web service sin embargo haciendo un debgu con los que hicieron el web service me indican que ellos reciben la peticion correctamente la procesan y nos la envian. Pero al message broker no esta regresando nada en el nodo Soap Async Response. Alguien tiene alguna idea de lo que podria estar pasando ?
Agradezco de antemano su ayuda
Gracias. |
|
| Back to top |
|
 |
| ashoon |
| Posted: Thu Apr 16, 2009 2:15 pm Post subject: |
|
|
Master
Joined: 26 Oct 2004
Posts: 235
|
trato soapui.org - yo creo la servicio no supporte ws-addressing
_________________
IBM Certified - SOA Solution Designer & WebSphere Datapower SOA Appliances |
|
| Back to top |
|
|
| mpaucara |
| Posted: Thu Apr 16, 2009 2:23 pm Post subject: |
|
|
Newbie
Joined: 23 Mar 2009
Posts: 3
|
How do I know if a web service support ws-addressing?
They have tried with a client asyncrhonus in .net/ and a client asyncrhonus in java then it worked fine for them. I need evidence to demostrate that the error is from they. |
|
| Back to top |
|
|
| ashoon |
| Posted: Thu Apr 16, 2009 2:29 pm Post subject: |
|
|
Master
Joined: 26 Oct 2004
Posts: 235
|
post their wsdl - the ws-addressing portion would be in the wsdl!
_________________
IBM Certified - SOA Solution Designer & WebSphere Datapower SOA Appliances |
|
| Back to top |
|
|
| mpaucara |
| Posted: Thu Apr 16, 2009 2:37 pm Post subject: |
|
|
Newbie
Joined: 23 Mar 2009
Posts: 3
|
| Code: |
<wsdl:definitions xmlns:s0="http://tempuri.org/Opeaciones.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="ConcatenarWebService" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="ConcatenarWebService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/Opeaciones.xsd">
<s:element name="ConcatenarRequest">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="parametroA" type="s:string"/>
<s:element minOccurs="0" maxOccurs="1" name="paremetroB" type="s:string"/>
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
<s:schema elementFormDefault="qualified" targetNamespace="ConcatenarWebService">
<s:element name="ConcatenarResult" type="s:string"/>
</s:schema>
</wsdl:types>
<wsdl:message name="ConcatenarSoapIn">
<wsdl:part name="concatenarRequest" element="s0:ConcatenarRequest"/>
</wsdl:message>
<wsdl:message name="ConcatenarSoapOut">
<wsdl:part name="ConcatenarResult" element="tns:ConcatenarResult"/>
</wsdl:message>
<wsdl:portType name="ConcatenarWebService">
<wsdl:operation name="Concatenar">
<wsdl:input message="tns:ConcatenarSoapIn"/>
<wsdl:output message="tns:ConcatenarSoapOut"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ConcatenarWebService" type="tns:ConcatenarWebService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="Concatenar">
<soap:operation soapAction="ConcatenarWebService:concatenarIn" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ConcatenarWebServicePort">
<wsdl:port name="ConcatenarWebService" binding="tns:ConcatenarWebService">
<soap:address location="http://.../wsaddressing/WSContrato.asmx"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> |
|
|
| Back to top |
|
|
| goffinf |
| Posted: Fri Apr 17, 2009 12:52 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
OK, so no WS-Addressing headers are specified either for the request or response according to this WSDL. Of course that doesn't mean that the service endpoint isn't emitting them (or expecting them) just that they are not specified within the technical service contract (WSDL).
If you are relying on the behaviour of the run-time you are using and that run-time takes it specification from WSDL, then you clearly need to specify all mandatory payload and meta-data information items. In the case of WS-Addressing these are the wsa:To and wsa:Action headers (for a request).
Fraser. |
|
| Back to top |
|
|
|
|
