I have implemented a simple POJO that receives messages using the documented setup via Jencks, and it seems to work well.
However what I really need is to implement a standard request/response, where the POJO (well I guess it isn't really a POJO anymore :) Responds to the request via the standard reply-to mechanism. (Usually to a temporary queue created by the requestor). This would seem like a very standard thing to do, however I can't find any examples or documentation on what the best way to do this is using Jencks. I see the docs on outbound messaging, should I just combine that with the inbound messaging? Seems a little inefficient. The unit tests have a request/reply test, but they reply uses a handbuilt session, not using jencks at all. Any help or pointers to a real application using Jencks this way would really be appreciated. Thanks. -- View this message in context: http://www.nabble.com/Request-reply-best-practice--tf4472120.html#a12751169 Sent from the jencks - user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
