Jul 10th, 2012, 08:47 AM
JSON Rest Web Service + JMS Queue best practice
I am trying to write web service that accepts requests, persists them on DB and for each request puts a message in a JMS queue for further processing (e.g. an external web app would call my web service "create request" providing JSON details for the request, the web service would persist the request and it would then create a message in the JMS queue for further asynch processing).
I have managed to create the JSON web service for creating and storing the request and I have succesfully implementented a test JMS queue. I would like to ask advice on how to tie the two pieces together. I would say that the best place to write the code for creating the JMS message is the request controller, am I correct or is there a better way to tie the two components?
I would also like to ask if anybody has seen a similar use case example and can share it.
Tags for this Thread