SoapExtensions allow you to intercept a web service call on teh way in or the way out (in fact they work on both the client and the server).
They are very useful for processing a service content irrespective of teh actual implementation. For example you could use them to log all messages to a database, or to perform schema validation on a message content.
Consider the case where you have two independent objects that need to process the same message, but neither should know about the other's existence, because they could be independently deployed.
Current WS implementations and tools do a lousy job of supporting loosely-coupled service design.
One thing you can do is implement an ISAPI filter to intercept the calls
another option is to implement a gateway so that a front web-service will get called and it would dispatch the call to the intended webservice and to whatever other listener you want
The webservice by default processes all messages it receives. Are you looking to store all the messages received and process them separately It would not be requried if that is what you are looking at.
Can you describe what you are trying to accomplish
How to listen to a web service for a message receive.
How to listen to a web service for a message receive.
cllard
madpower2000
You can implement a SoapExtension.
SoapExtensions allow you to intercept a web service call on teh way in or the way out (in fact they work on both the client and the server).
They are very useful for processing a service content irrespective of teh actual implementation. For example you could use them to log all messages to a database, or to perform schema validation on a message content.
Jakin
Consider the case where you have two independent objects that need to process the same message, but neither should know about the other's existence, because they could be independently deployed.
Current WS implementations and tools do a lousy job of supporting loosely-coupled service design.
Aravinth Kulasekaran
One thing you can do is implement an ISAPI filter to intercept the calls
another option is to implement a gateway so that a front web-service will get called and it would dispatch the call to the intended webservice and to whatever other listener you want
Arnon
RedHedToo
ScottLeo
The webservice by default processes all messages it receives. Are you looking to store all the messages received and process them separately It would not be requried if that is what you are looking at.
Can you describe what you are trying to accomplish