Hi,

I am working on a project which is developed using Play Framework. The
project needs to interact with a number of third party SOAP services. It is
very important for the system to be scalable by design and should allow
high number of concurrent requests. I understand that this can be achieved
using Async HTTP Transport.

For now, I am using Java interfaces and classes generated through wsdl2java
utility. Currently I have generated services with synchronous calls. I plan
to use -asyncMethods switch and generate asynchronous services.

I am trying to figure out how I can manage the threads used by async web
service calls.

Few questions I have are,

1. How can I control the thread pool / executor used by the WS client?
2. How can I shared the same thread pool / executor across multiple clients?
3. Does the Async HTTP transport use another thread pool / executor? Can it
also share the same with rest of the WS clients?
4. Do I need to create a spring config and create all the client beans
there to be able to manage them through single CXF instance (bus)? I wonder
if it is a good idea to independently create WS client instances?

Overall I hope I am not doing anything fundamentally wrong. I hope that
using async client methods and async transport the system will allow
multiple concurrent calls.

Thanks,

Kalpak

Reply via email to