I agree with your suggestion; it is much better clean design approach.
On Fri, Oct 16, 2020 at 8:34 PM Shafreen <anfar.shafr...@gmail.com> wrote: > Hi All, > > Any opinion on this? > > On Sun, Oct 11, 2020 at 11:45 AM Shafreen <anfar.shafr...@gmail.com> > wrote: > >> Hi All, >> >> Each Message Forwarding Processor must have a target endpoint. At the >> moment we configure this target endpoint by adding a property in the >> in-sequence of proxy service as follows. >> >> <property name="target.endpoint" value="StockQuoteServiceEp" /> >> >> IMO, this way of associating target-endpoint with Message Forwarding >> Processor is not only error prone but also less readable. Therefore, I >> think we can improve configuring target endpoint by making it at an >> attribute of the Message Forwarding Processor as follows, >> >> <messageProcessor class= >> "org.apache.synapse.message.processors.forward.ScheduledMessageForwardingProcessor" >> name="ScheduledProcessor" messageStore="MyStore" >> *targetEndpoint="StockQuoteServiceEp"*> <parameter name="interval">10000 >> </parameter> <parameter name="max.deliver.attempts">3</parameter> < >> parameter name="max.deliver.drop">true</parameter> </messageProcessor> >> >> WDYT ? >> > -- Sent from Gmail Mobile
