ODE
  1. ODE
  2. ODE-286

Empty content of response message problem

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.2
    • Component/s: JBI Integration
    • Labels:
      None

      Description

      I have wsdl:

      <?xml version="1.0" encoding="UTF-8"?><Unable to render embedded object: File (-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><) not found.-- Generated by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS
      <types>
      <xsd:schema>
      <xsd:import namespace="http://ws/" schemaLocation="schema.xsd"></xsd:import>
      </xsd:schema>
      </types>
      <message name="testOper">
      <part name="parameters" element="tns:testOper"></part>
      </message>
      <message name="testOperResponse">
      <part name="parameters" element="tns:testOperResponse"></part>
      </message>
      <portType name="InvokedWebService">
      <operation name="testOper">
      <input message="tns:testOper"></input>
      <output message="tns:testOperResponse"></output>
      </operation>
      </portType>
      <binding name="InvokedWebServicePortBinding" type="tns:InvokedWebService">
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"></soap:binding>
      <operation name="testOper">
      <soap:operation soapAction=""></soap:operation>
      <input>
      <soap:body use="literal"></soap:body>
      </input>
      <output>
      <soap:body use="literal"></soap:body>
      </output>
      </operation>
      </binding>
      <service name="InvokedWebServiceService">
      <port name="InvokedWebServicePort" binding="tns:InvokedWebServicePortBinding">
      <soap:address location="http://localhost:13195/services/InvokedWebServiceService"></soap:address>
      </port>
      </service>
      </definitions>

      and schema:

      <?xml version="1.0" encoding="UTF-8"?><!-- Published by JAX-WS RI at http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.3.1-hudson-417-SNAPSHOT. --><xs:schema xmlns:tns="http://ws/" xmlns:xs="http://www.w3.org/2001/XMLSchema" ver

      <xs:element name="testOper" type="tns:testOper"></xs:element>

      <xs:element name="testOperResponse" type="tns:testOperResponse"></xs:element>

      <xs:complexType name="testOper">
      <xs:sequence></xs:sequence>
      </xs:complexType>

      <xs:complexType name="testOperResponse">
      <xs:sequence></xs:sequence>
      </xs:complexType>
      </xs:schema>

      ... and I try to invoke testOper from flow. I got response but then process suspend or something like this. This scenario works on axis version. It looks like the problem is that response has only element without content.

      In logs I've got:

      8-05-20 16:17:05,153 DEBUG - HttpComponent - Received exchange: status: Active, role: provider
      2008-05-20 16:17:05,154 DEBUG - HttpComponent - Retrieved correlation id: null
      2008-05-20 16:17:05,352 DEBUG - header - >> "POST /services/InvokedWebServiceService HTTP/1.1[\r][\n]"
      2008-05-20 16:17:05,353 DEBUG - header - >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
      2008-05-20 16:17:05,354 DEBUG - header - >> "Content-Length: 196[\r][\n]"
      2008-05-20 16:17:05,355 DEBUG - header - >> "SOAPAction: ""[\r][\n]"
      2008-05-20 16:17:05,355 DEBUG - header - >> "User-Agent: Jakarta Commons-HttpClient/3.0[\r][\n]"
      2008-05-20 16:17:05,356 DEBUG - header - >> "Host: burek.touk.pl:13195[\r][\n]"
      2008-05-20 16:17:05,357 DEBUG - header - >> "[\r][\n]"
      2008-05-20 16:17:05,357 DEBUG - content - >> "<?xml version='1.0' encoding='UTF-8'?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><testOper xmlns="http://ws/" xmlns:tns="http://ws/" /></env:Body></env:Envelope>"
      2008-05-20 16:17:05,371 DEBUG - header - << "HTTP/1.1 200 OK[\r][\n]"
      2008-05-20 16:17:05,372 DEBUG - header - << "X-Powered-By: Servlet/2.5[\r][\n]"
      2008-05-20 16:17:05,372 DEBUG - header - << "Server: Sun Java System Application Server 9.1_02[\r][\n]"
      2008-05-20 16:17:05,373 DEBUG - header - << "Content-Type: text/xml;charset="utf-8"[\r][\n]"
      2008-05-20 16:17:05,373 DEBUG - header - << "Transfer-Encoding: chunked[\r][\n]"
      2008-05-20 16:17:05,374 DEBUG - header - << "Date: Tue, 20 May 2008 14:17:05 GMT[\r][\n]"
      2008-05-20 16:17:05,375 DEBUG - content - << "9"
      2008-05-20 16:17:05,375 DEBUG - content - << "a"
      2008-05-20 16:17:05,376 DEBUG - content - << "[\r]"
      2008-05-20 16:17:05,376 DEBUG - content - << "[\n]"
      2008-05-20 16:17:05,377 DEBUG - content - << "<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><testOperResponse xmlns="http://ws/"/></S:Body></S:Envelope>"
      2008-05-20 16:17:05,378 DEBUG - SedaFlow - Called Flow send
      2008-05-20 16:17:05,153 DEBUG - BpelInstanceWorker - Starting worker thread Thread[ODEServerImpl-8,5,main] for instance IID

      {http://odeservicestest.com/testProcess/ODE}

      ODE-8#2803
      2008-05-20 16:17:05,436 DEBUG - BpelInstanceWorker - Doing work for instance

      {http://odeservicestest.com/testProcess/ODE}

      ODE-8#2803 in thread Thread[ODEServerImpl-8,5,main]
      2008-05-20 16:17:05,441 DEBUG - BpelInstanceWorker - Finished work for instance

      {http://odeservicestest.com/testProcess/ODE}

      ODE-8#2803 in thread Thread[ODEServerImpl-8,5,main]
      2008-05-20 16:17:05,442 DEBUG - BpelInstanceWorker - Worker thread Thread[ODEServerImpl-8,5,main] for instance IID 2803 ran out of work.

      So it looks like ode treat this exchange like some other then in/out pattern.

      I works on trunk version but it also have done on 1.1.1 version.

      Regards, Arek

      1. emptyresp.tar.gz
        48 kB
        Arkadiusz Burdach

        Activity

          People

          • Assignee:
            Matthieu Riou
            Reporter:
            Arkadiusz Burdach
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development