I will talk to our design team about a lightweight workflow system. I really want a unique transactionID generated by the client to follow the SOAP calls throughout our backend provisioning systems. I just don't know how to embed it in the SOAP message. We had an XML over HTTP architecture and we embedded a transactionID in *every* XML schema we passed around. I could add a transactionID to *every* SOAP call but that is not a good solution. I really want it outside of the content.
I could use the MessageID in WS-Addressing if I can set it programmatically but I have not found a way to intercept the MessageID creation. I can read it before it goes out but I don't see how to set it prior to sending the SOAP message. Is this possible? Thanks for the ideas, jeff -----Original Message----- From: Bryan Kearney [mailto:[email protected]] Sent: Tuesday, March 17, 2009 4:32 PM To: [email protected] Subject: Re: Tacking messages across several SOAP Request [email protected] wrote: > Thanks Andrew. > > I am attempting to do this without a "home-grown" solution. If this can be > done using WS-Addressing or some other well-known method I will be happy. As > a last resort I will be writing something like you did. > > Thanks, > > Jeff Can you use a light weigh orchestration/workflow system? This seems to be what BPEL was designed for. -- bk
