Hi Gul, Yes, In your scenario Axis2 creates two thread , then both thread invokes the same istance of the class implementing the service, so if the methods of this class are not synchronized the state of the service is not thread-safe. This is the mechanism for every kind of MessageReceivers.
Francesco 2007/6/1, Gul Onural <[EMAIL PROTECTED]>:
Is Axis2 thread-safe for "application" scope services that use RawXMLMessageReceivers? Basically I am wondering what happens if two clients invokes the same operation on that type of service. Does Axis2 create 2 different threads to invoke service's implementation method for that operation? Gul
