ESB Itinerary transform response ‘was not a valid map type’

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › ESB Itinerary transform response ‘was not a valid map type’

Viewing 1 reply thread
  • Author
    Posts
    • #23449

      I’ve been
      struggling with this one for the past few days, without results. Here’s the
      situation.

      I’ve got
      an Itinerary that I made with the ESB Toolkit 2.0 to call a WCF service.

      • On-Ramp
        • Messaging
          Extender to transform request
        • Messaging Extender to route the message to the service
      • Off-Ramp
        extender as a send port filter
      • Off-Ramp
        • Messaging
          Extender to transform response

      Pretty
      straightforward, but I can’t seem to get the last transform working. Biztalk
      throws the following exception:

      There was
      a failure executing the send pipeline:
      “Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySendPassthrough,
      Microsoft.Practices.ESB.Itinerary.Pipelines, Version=2.0.0.0, Culture=neutral,
      PublicKeyToken=31bf3856ad364e35” Source: “ESB Dispatcher” Send
      Port: “DynamicResolutionSolicitResp” URI: “http://msdev64.domein.netaspect/CertigoServiceStub/TestIdService.svc”

      Reason: The type
      for Certigo.Gateway.Party.Maps.TestMapResponse,Certigo.Gateway.Party,
      Version=1.0.0.0, Culture=neutral, PublicKeyToken=751770c464b878df was not a
      valid map type.

      I’ve
      started out with a map that mapped the actual service response to a business
      object of ours and ended up creating a simple service with only one string
      parameter and one string as a response to exclude the possibility that
      the map was indeed invalid. But this had no results.

      If I
      remove the last transform, the Itinerary works fine and when I save the
      resulting XML to file and put it in the Map that I used in the last transform
      it maps fine. So I’m kinda lost…  especially since the request maps fine
      also…

      Any ideas?

    • #23453

      I finally made some progress. I reinstalled the ESB Core application and created the Global.ESB sample application using the Dynamic Resolution and Resolver Service samples.

      I solved the problem mentioned in my previous post by loading the maps into the Global.ESB application, since the DynamicResolutionSolicitResp send port is in there and it needs to know about my maps and schema’s. No more exception, but no response either.

      While doing a file compare of the sample Itineraries and my own I discovered that mine had a different Guid for the DynamicResolutionSolicitResp send port and a (read only?!) property called “isRequestResponse” set to “true” (where mine stated “false”).

      Solution was to set isRequestResponse to true on the Off-Ramp extender that I used as a send port filter.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.