All, I this is a combination "how would I" and/or "request for enhancement", if I can't.
We currently use Apache SOAP 2.2 and a whole schlew of clients -- VB (w/ server tweaks) and Java and Perl and such. We like this (for what it is) but we have one main runtime management problem. When problems occur (a bad parameter, a bad password, a rogue client, whatever) we can know/log the soap parameters ----- but not which client/host is making the request. As such -- we are not able to track down (nor block at firewall) a culprit -- nor proactively help a customer. Yes we could attempt to match the HTTP log w/ the SOAP calls, but that [with a busy server] is adhoc, at best. Perhaps (with AXIS using logging) we could re-configure AXIS on the fly, to capture information, however we do NOT want all requests --- just those that cause us a problem at the higher level/later point. Can we (by tying our services to our AXIS server & transport) access the "session" or "request" -- or something else (some abstracted "user context object" in AXIS)? BTW: Is "keeping the called server-side code unaware of the calling AXIS server" a design goal, or just a nicety (brought about by the server introspecting) that isn't necessarily desired or not. Is there -- or could there be -- an "AxisServierSideService" interface I could implement, or something I could sub-class from, to be server/session/request aware? Alternatively [feature request] could the AXIS server set relevant client information (e.g. IP and/or others) in the log4j Nested Data Context [for the running thread] prior to calling my class? This way if I log a message it will be bound to the client information without me having to do anything special. Other ideas appreciated. Thanks in advance. regards, Adam -- Open Business Interchange: <http://www.openbiz.biz> The Revolutionary B2Bi Web Service ...
