Hi Bernd. In this case you need an endpoint in the client that allows the service to call back to it when the work is done (the service then becomes a client and the client then becomes a service).
When the client does a send of the original work, I'd expect it to set the MessageID in the outgoing message. When the service sends back a response eventually, it sets the RelatesTo field in the response message and the client can use that to correlate the response with the original request.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200336#4200336
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200336
"ataylor" wrote : anonymous wrote : It should be better if netty can provide the support so that we don't have to handle the details in JBM.
|
| That would be nice but we need this asap and netty only has a basic http implementation.
True we need this ASAP, but the work is a generic piece of work (Netty Servlet proxy), so it can still be done in the Netty project, even if the work is completed by a JBM team member.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200270#4200270
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200270
I think this would be confusing.
Say.. the PostOffice stays stand alone in production for 2 weeks till someone accidentally drops a file with a clustered Queue. We would need to transform the PostOffice into a clustered one, from opening the JChannels to filling all the states. (Without also considering other implications on the data already existent on the DB).
But even if that was not an issue, it would require some development (mainly testing) on the PostOffice. IMO it would be better to use that energy towards 2.0.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200186#4200186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200186