wood burning stoves 2.0*
The moose likes Web Services and the fly likes which java stack to use for multithread JAXWS web services client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "which java stack to use for multithread JAXWS web services client" Watch "which java stack to use for multithread JAXWS web services client" New topic
Author

which java stack to use for multithread JAXWS web services client

Meir Yan
Ranch Hand

Joined: Apr 27, 2006
Posts: 597
i need to build multi threaded web service client that based on jaxws framework as the ws provider.
this client will send ws request to different endpoint .
and in each end point it will send to same ws function different parameters and it will return the answer in sync way.
is there any framework that i can build on that will handle me the thread pool and the connections .
or do i need to build the server my self ? the client needs to be kind of server because it will do checks ( on local db ) with a thread that iterate and checks for updates in local db.
how do i need to approach such task .
Thanks
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
Metro deployed to Tomcat or GlassFish will suffice.
In fact, I suspect that any web service stack that adheres to the JAX-WS standard and can be run in a servlet container will also suffice.
You do not have to implement the server yourself, since this will be taken care of by the servlet container.
Best wishes!


My free books and tutorials: http://www.slideshare.net/krizsan
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: which java stack to use for multithread JAXWS web services client
 
Similar Threads
what is faster with when representing structure
Problem about running jar file from netbean dist directory
How to build a rule based Monitoring Servlet
Authenticate and authorise access to webservices
Is it necessary to expose a webservice at UDDI if both the service and client know each other ?