Hi Team, I have updated more information in stackoverflow for the same subject about my findings but still i am unable to solve this issue :(. I am trying my best but still no luck. can someone please share some information?
https://stackoverflow.com/questions/64546033/exchange-notify-event-exchange-option-deprecated-in-camel-3-4-and-looking-for-al I also posted a new question incase if someone can help me. https://stackoverflow.com/questions/64583050/close-all-the-aggregated-groups-after-file-split-is-complete-in-camel-2-24 Thanks On Wed, Oct 28, 2020 at 9:15 AM tech tdeveloper <techtdevelo...@gmail.com> wrote: > Hi Team, > > I have been using the Camel 2.24 in my application for some time and I was > trying to migrate the camel version from 2.24 to 3.4. The reason for this > migration is, the latest version has many great features in aggregate where > I am more interested like "AGGREGATION_COMPLETE_ALL_GROUPS" and etc. > > If i upgrade to 3.4, i am able to use all these options and its working > like a magic but the problem here due to this upgrade is, I have been using > Exchange.NOTIFY_EVENT option in the below method to not notify the exchange > again because i am calling this method under eventnotifier. so i do not > want to be notified again when an exchange is getting created. but when i > upgrade to 3.4, this Exchange.NOTIFY_EVENT is not working and looks like it > has been deprecated. I tried my best to identify the > replacement/alternative of this but was unable to get the information. So I > would like to see the replacement or alternative of this and it would be > really helpful if some one of you please give a hand to solve this. Since > it's quite urgent, it would be really appreciated if i get the response. > > String response = (String) producerTemplate.sendBodyAndProperty("event", > ExchangePattern.InOut, inputPayload, Exchange.NOTIFY_EVENT, Boolean.TRUE) > > I did ask this question in stackoverflow but still not getting the > response. since it quite urgent, can someone of you please give a hand to > solve this? Really appriciate your response!. > > > > > > > > "AGGREGATION_COMPLETE_ALL_GROUPS" and etc. if i upgrade to 3.4, i am > able to use all these options and work like a magic. but the problem here > is, >