Results 1 to 3 of 3

Thread: Message publishing interceptors, participate on same message history

  1. #1

    Default Message publishing interceptors, participate on same message history

    Hi Guys,

    in my application I use <int:message-history/> to track the message history and so far it is working fine for my requirement. Then another request came that they want to publish the out put of the final result. In my application there are more than one service activator and depending on the condition (xpath-router) i am redirecting incoming message to relevant service activator. according to new requirement all of the service activators should publish their final result to one channel. I tried this with Message publishing interceptors (@Publisher), but every time publisher create the new message and start new messaging entry, so the message history of this message will not participate with original message history. is there any way of instructing the @Publisher that we want to participate the newly created message in original messaging context?

    Thanks,
    Kelum

  2. #2

    Default

    Hi Guys,

    same thing happens when an exception occurs. it creates a new message and start new message flow, then again original message history is lost. What do you guys think about this?

    thanks,
    kelumt

  3. #3
    Join Date
    Mar 2010
    Location
    Gtr Philadelphia, PA
    Posts
    2,037

    Default

    Re: Publisher - why can't you simply set the output-channel on each service-activator to the same channel?

    Re: Error flow - the new Message has a payload MessagingException, which has two properties (cause and failedMessage). The failedMessage has all the headers (including messageHistory), at the time the failure occurred.
    Gary P. Russell
    Spring Integration Team
    SpringSource, a division of VMware

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •