Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-18144

camel-milo: Update Eclipse Milo from 0.3.7 to 0.6.6

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Dependency upgrade
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 3.17.0
    • 3.18.0
    • camel-milo
    • None
    • Unknown

    Description

      Update Eclipse Milo from 0.3.7 to 0.6.6.

      Out of my perspective, there were significant changes, especially the timing of the notifications (client subscription) seems to behave slightly different using Eclipse Milo 0.6.6 (or is subject to a misunderstanding on my side), e.g. there is an additional, early notification with a node value "null" after route-startup, as at this time the node value hasn't been set yet. I saw these kind of timing issues with 0.3.7, too, but less often. In order to avoid changing the unit tests too much, I introduced a new omitNullValues parameter on the client endpoint, which defaults to "true" in order to avoid that notification and to avoid flaking unit tests, too.

      Would be great if somebody out there with experience with Eclipse Milo could test that in specific scenarios, too.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            andreas.klug2@de.bosch.com Andreas Klug
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment