Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-495

Message for <receive> activity is not needed anymore if we send a SOAP message for <receive> before <pick> activity

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.3.6.Final, 2.4.0, 3.0.0.M3
    • 2.3.4.Final, 3.0.0.M2
    • ODE
    • None

    Description

      The structure of process:
      <sequence>
      <pick>
      <receive>
      </sequence>

      Messages for <receive> and <pick> has to have same correlation IDs.

      If we send message for <receive>, the riftsaw remember the message and after we send a message for <pick>, the process is completely performed.
      I think this approach is right but the issue is that the riftsaw remember the message forever and if I send the message for <pick> once again with the same correlation ID, the process is completely performed without any needs of message for <receive> activity.

      Attachments

        Issue Links

          Activity

            People

              jeff.yuchang_jira Jeff Yu (Inactive)
              ibek1@redhat.com Ivo Bek
              Archiver:
              rhn-support-adandapa Aitik Dandapat

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty