hi, it seems that the problem with operation name is resolved in CXF producer ( Fuse-3.3.1.13 ) , now it extracts operationName from the payload, so it is not important that operation name is null after jms endpoints
btw, I tried to set redelivery policy for ActiveMQ in activemq.xml but I couldn't do work. I would appreciate any example. best regards javier Lukasz Lichota wrote: > > how are you going to verify that target service received the message? > based on the fact that there was no exception? > > I think it may be possible to use to approach you chose, you can use EIP > Static Recipien List > http://servicemix.apache.org/servicemix-eip.html#servicemix-eip-StaticRecipientList > > now if you use SRL after JMS Consumer (and have multiple CXF Providers) > your transaction will be rolled back on any fault on call of any provider, > thus if the third provider fails, message will be send once again and > first and the second service will receive this message again, > > to make it a bit better you could use separate transaction for each target > that is to have SRL before JMS Provider, so you would have > JMSProvider/Consumer/CXFProvider chain for each of the target services > > other question is what MEP is used by JMS consumer by default, what you > need is Robust-In-Only becaue with In-Only you never get faults. > You can specify this MEP using marshaller > http://servicemix.apache.org/servicemix-jms-new-endpoints.html but maybe > it's done like that by default, > Ashwin, do you know? > > best regards > Lukasz > > PS. also please note that you can configure redelivery policy for ActiveMQ > in activemq.xml > > PS2. Your flow will be a bit complicated so taking look at Camel is also > an option > > -- View this message in context: http://www.nabble.com/operation-name-is-null-after-jms-endpoints-tp21713138p21790463.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
