What about wrapping up a static method and making it available as a web service? Do you see any drawbacks, incompatibilities or problems with such an approach?
Thread-safety - parallel web service requests would cause collisions that are easily avoided with separate object instances. Trying to synchronize static invocations would negatively impact scalability.
As web services are supposed to be stateless there is no equivalent concept to Java's "static". If you use a correlation identifier to tie together separate web service invocations then that is a matter of your business process, not something that the web service interface itself is concerned with as it can support correlation IDs through regular capabilities.
I promise I will be the best, most loyal friend ever! All for this tiny ad: