Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Asynchronous web service using RESTEasy  RSS feed

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Guys,
It would be great if somebody is having a simple example for Asynchronous webservice using resteasy(RESTFul Web Services implementation of JBOSS). I am able to create synchronous webservice using resteasy, it is working fine.

My Objective is to find out a way to implement Asynchronous web service for batchjobs.

By googling, I find out 2 strategies.
1. Polling
2. Callback Strategy.

Probably "Callback Strategy" might be the right choice for bacth job. Correct me If I am wrong.

Please help.


-Amit
 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
I cannot help you with the asynchronous web service client using RESTEasy.
However, what immediately comes to my mind when you say "batch job", "REST" and "asynchronous" is the following scenario:
- A batch job is submitted to the job resource.
- In connection to the job being submitted, another resource is created which (eventually) will hold the result of the job.
- The URI to the resource that will hold the result of the submitted job is returned to the client that submitted the job as part of the response to the request that submitted the job.
- The client then polls the URI (job result resource) for the result.

The above scenario is easier to implement than a "callback" version, in which the client would need to have a REST web service to which the batch job processor could submit (create) job results (job result resources).
However, if polling is undesired, implementing a "callback" version is certainly doable.
Best wishes!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!