Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.10, 4.11
    • Fix Version/s: 4.11 CP2
    • Component/s: Rosetta
    • Labels:
      None

      Description

      I have an EBWS based service which is using the SyncServiceInvoker to call a second service. This all works fine but if I throw an exception after the SyncServiceInvoker call the exception is not propagated to the client as a soap fault.
      However if I remove the invocation of the SyncServiceInvoker and throw an exception, a soap fault is sent to the client.
      I have attached a test project which demonstrates this.

      To see the fault just comment out the SyncServiceInvoker call.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  tadayosi Tadayoshi Sato
                  Reporter:
                  jshepher Jason Shepherd
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: