The final idea is send in-only messages from a cxf application to serveral cxf applications. All target applications need to receive the message. If there is any down, smx has to resend the message. So, first I thought to use "Recipient List" pattern using camel ( CXF consumer - Camel - CXF producer) but how can I resolved the case in smx is down? Using XA? There is not a clear example, and the smx documentation is very poor. Then I thought to use topic queues in the middle and use camel to resend messages, but I have the problem with operation names. What do you think about this case?
Lukasz L. wrote: > > yeah, I didn't noticed that it's transacted, which is a good option for > persistence, I'm not sure but probably you also need to add > synchronous="true" on the consumer (because when it's asynchronous > transaction ends after sending message not after received status DONE from > CXF provider), > > but to better answer you question, can you say what do you want to achieve > here? > is that in-only invocation? if yes but you care if the invocation > successful, maybe it's better to design target service to send > confirmation, that is make it in-out? > if you don't care if target service invocation was successful, then you > probably don't need persistence on the bus (just CXF consumer - provider > pair), probability that SM crashes during such invocation would be very > low, > -- View this message in context: http://www.nabble.com/operation-name-is-null-after-jms-endpoints-tp21713138p21754301.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
