WF Service Envelope Diagnostics RRS feed

  • Question

  • Hello,

    I have a WF service that works wonderfully from .Net clients. However I am struggling getting an android client using Java to work. One reason is because Msoft does so much work for me serializing a SOAP request. Well my difficulty I am sure is that I am serializing something wrong or in some way my soap envelope is malformed. In java I can get the msg body as such:

    <v:Envelope xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:d="http://www.w3.org/2001/XMLSchema" xmlns:c="http://schemas.xmlsoap.org/soap/encoding/" xmlns:v="http://schemas.xmlsoap.org/soap/envelope/">
        <v:Header />
            <LiftDataExchange xmlns="http://tempuri.org/" id="o0" c:root="1">
                <UserName i:type="d:string">STERILIZED_OUT</UserName>
                <Password i:type="d:string">STERILIZED_OUT</Password>
                <ExerciseProgramID i:type="d:string">STERILIZED_OUT</ExerciseProgramID>
                <IncomingWorkoutData i:type="d:string">STERILIZED_OUT</IncomingWorkoutData>
                <Action i:type="n0:ExchangeEnumerations" xmlns:n0="http://schemas.datacontract.org/2004/07/IronMikeDataExchangeWorkflowService.Enum">GetNextWorkout</Action>

    How would I get the same from the Msoft client so I can compare the two to possibly figure out what I am doing wrong.



    Tuesday, January 29, 2013 3:52 PM


  • If you need to log wcf messages, you need to enable Tracing and Message Logging.

    Or, if you use HTTP protocol, you could just use Fiddler to capture traffic and analyze Envelope.

    • Marked as answer by Molly Chen_ Tuesday, February 5, 2013 8:50 AM
    • Unmarked as answer by Molly Chen_ Tuesday, February 5, 2013 8:50 AM
    • Marked as answer by Molly Chen_ Monday, February 18, 2013 4:20 AM
    Wednesday, January 30, 2013 12:02 PM