[CAMEL-12587] camel-zipkin-starter fails mapping service names

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.22.0
• Fix Version/s: 2.22.1, 2.23.0
• Component/s: camel-zipkin
• Estimated Complexity: Unknown
• Assignee: Viral Gohel
• Reporter: Adrian Cole
• Created: 18/Jun/18 08:20
• Updated: 13/Aug/18 15:36
• Resolved: 13/Aug/18 15:36

Description

camel-zipkin-starter uses mapped properties for service names. For example, the following wildcard properties are used in camel-example-zipkin

camel.zipkin.server-service-mappings.*=service1
camel.zipkin.client-service-mappings.*=service2

 

trunk is currently broken, as running the service1 part of the example ends with errors like so unless you comment out the mappings:

 

Caused by: org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [java.lang.String] to type [java.util.Map<java.lang.String, java.lang.String>] at org.springframework.core.convert.support.GenericConversionService.handleConverterNotFound (GenericConversionService.java:321) at org.springframework.core.convert.support.GenericConversionService.convert (GenericConversionService.java:194) at org.springframework.boot.context.properties.bind.BindConverter$CompositeConversionService.convert (BindConverter.java:162) at org.springframework.boot.context.properties.bind.BindConverter.convert (BindConverter.java:96)

Issue Links

• links to: GitHub Pull Request #2470
• links to: GitHub Pull Request #2470