Andreas Klug created CAMEL-18144:
------------------------------------
Summary: camel-milo: Update Eclipse Milo from 0.3.7 to 0.6.6
Key: CAMEL-18144
URL: https://issues.apache.org/jira/browse/CAMEL-18144
Project: Camel
Issue Type: Dependency upgrade
Components: camel-milo
Affects Versions: 3.17.0
Reporter: Andreas Klug
Fix For: 3.18.0
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.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
