Thank you for your suggestions. The server at B can have axis2 in it (hence intermidiate web-service that can intercept soap headers etc). What I am really concerned about is attachments. I expect to have large attachments, both ways.
Unfortunately I am new to web service and not familiar with ws-addressing yet, -so its a learning process, -I am trying to create an intermidate service, and probably have to experiment a bit to see if it works. Thanks again, S On 7/9/07, Walker, Jeff <[EMAIL PROTECTED]> wrote:
The 'standard' web service solution I believe, is to write some SOAP header handlers, deploy them at B, and they take care of logging, they then pass the request onto the actual web service impl at C, if certain required checks pass. This is the whole point of SOAP headers, I think. They take care of pre (and post) processing like logging and auditing, in your domain. (Doesn't WS-Addressing do something like this?) Having said that, you have a plain HTTP server at B and not an intermediate web service that catches all requests (which is what most SOA architects would recommend, I think). Can the HTTP server have functionality added to it? Your HTTP server at B should be able to intercept the HTTP request bound for the web service at C and at least log the request. This is a fairly basic function of any HTTP server. (I once had a simliar kind of situation, but in our case, we were using 2-way SSL and the cert had to be extracted, checked and the request decrypted at the http server, which was forwarded to our web service). ------------------------------ *From:* Sanoran Triamesh [mailto:[EMAIL PROTECTED] *Sent:* Monday, July 09, 2007 2:24 PM *To:* [email protected] *Subject:* Re: [Axis2] How to forward a SOAP message We are a big defense company and have very restrictive internet access. I have to create a pc/desktop client (A) to a web service (C) that inside a isolated lan, and can only access C via an intermidiate http server (B). Also, I have to log/monitor requests at B and convince security people that they can intercept/monitor the requests. I am sure there are many solutions possible, but I am also new to web services. So my proposal was to have A send a SOAP/http request to B, where there will be a 'proxy' service that will send the request to C. Synapse could be an axis service running inside B redirecting and allowing monitoring. I would, of course, not want to code anything on B but rather use an existing solution. Feel free to suggest alternatives (off line if you wish, [EMAIL PROTECTED]). Thanks On 7/9/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > > Cant use synapse :( > > Can you explain? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
