|
From: David G. <dg...@co...> - 2003-08-06 16:40:42
|
I'll be building an interface to a soap web service API, and therefore I thought I should stop futzing around and actually look into building the pipeline. In starting to review the soap stuff, I've come across the some issues that I would appreciate those with years of experience (or even weeks will work) to comment on. I need to go through a (relatively) complicated process as follows: a. post soap document. Response is either transaction id or failure code. b. if transaction id, post soap queries for status of transaction until status = done. c. if failure code, indicate failure through some magic that I haven't thought of yet. I have the following questions: 1. The current soap writer ignores the reply. I'll need to change that, but I'd like to implement it such that it can be as generic as possible. Is there a description somewhere of how a stage writer should act? Or, lacking that, which is the best stage writer to use as a template for how the SoapWriter should be modified? 2. How should the reply be handled? Is there some current stage that I can use, or will I need to create my own stage to process the reply? If I need to roll my own, is there some guide lines to make it generic for general use, or should I just make it specific to my needs? Thanks, David -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |