Announcement Announcement Module
No announcement yet.
AbstractMessageBarrierHandler Question Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • AbstractMessageBarrierHandler Question

    I have been looking through the AbstractMessageBarrierHandler.processMessage code trying to extend the
    AbstractMessageAggregator and had a question about some code.
    In the AbstractMessageBarrierHandler.processMessage it looks like if the message received is the one right after the complete (i.e, canAddMessage is false), the message gets dropped? I could be missing something, but is this true? If you can't add the message to the barrier here, should it be discarded?


  • #2
    If you're going down this path you should check out:

    I found extending AbstractMessageBarrierHandler too difficult, so I've come up with a replacement.

    I've done the ground work for a new MessageStore backed component called BufferingMessageHandler I've used it to create replacements for the aggregator and resequencer.

    There is no namespace support for it yet, but it's ready for a spin.