Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: NIGHTLY
    • Fix Version/s: NIGHTLY
    • Component/s: Core
    • Labels:
      None

      Description

      Aggregate processor may give a control to user to process messages,which are stored in a message store, based on a correlation pattern.
      To use the aggregate processor, user should write a custom correlation class and should return back the correlated messages to the processor..

      For this , there are two required parameters are defined;
      <parameter name="sequence">send_seq</parameter>
      <parameter name="correlation.class">org.apache.synapse.message.processors.aggregate.TestCorrelation</parameter>

      So, the aggregate processor configuration would be;

      <messageProcessor class="org.apache.synapse.message.processors.aggregate.AggregateMessageProcessor" name="aggregateMsgPorcessor" messageStore="testMsgStore">
      <parameter name="interval">20000</parameter>
      <parameter name="sequence">send_seq</parameter>
      <parameter name="correlation.class">org.apache.synapse.message.processors.aggregate.TestCorrelation</parameter>
      </messageProcessor>

      Messages will be processed based on the defined sequence(eg: send_seq)

      This does not provide guaranteed delivery, since ' Forwarding processor' which provides that functionality..If user needs guaranteed delivery then he can define another 'Forwarding processor within the "sequence"..

      1. AggregateMessageProcessor.patch
        23 kB
        Vijayaratha Vijayasingam

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Vijayaratha Vijayasingam
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development