Dave Syer

I think it's a bug in the Maven javadoc plugin. I'll see if I can find a workaround, or maybe bump the plugin version or something.

Update: the workaround was to add `8` to the Javadoc plugin config.

I guess there's nothing stopping you from using the existing serdes, but Spring is more flexible with listener method signatures so you won't get the full benefit. The sample wouldn't...

> In that case, I think the test code has to be modified to use the byte deserializer in the listener instance. That's not the purpose of this test. The...

So where are we going with this? Isn't cloudevents-kafka already basically a "single encoder/decoder for each transport"? Anyway, here's a branch using the serdes from cloudevents-kafka: https://github.com/dsyer/sdk-java/tree/kafka-only. If you prefer...

I don't think we're on the same page here yet. I dislike the idea of adding encoders/decoders for every new transport, but that's the current design of Cloud Events and...

Can you be a bit more explicit about the use case? I'm not sure what you mean by "current configuration of endpoints". Is it just that the `ServiceInstance` doesn't contain...

I see (I think). There are potential lifecycle issues (e.g. MongoDB might be needed before the `DiscoveryClient` is available), but maybe that's nothing new. You would probably want your MongoDB...

Because all the features were moved to spring integration. Zookeeper leader election is first class over there now, and SI is (IMO) very broad, so I don't know why it...

Discovery is clearly part of spring cloud, but health is spring boot (note also the example above was about eureka, so not using zk for discovery). All of the other...