Tim Sexton created CAMEL-12836:
----------------------------------

             Summary: Type Converter Loader Exception: Elasticsearch-Rest 
cannot find any in package defined
                 Key: CAMEL-12836
                 URL: https://issues.apache.org/jira/browse/CAMEL-12836
             Project: Camel
          Issue Type: Bug
         Environment: Docker/K8s
            Reporter: Tim Sexton


{{Error creating bean with name 'servletEndpointRegistrar' defined in class 
path resource 
[org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]:
 Bean instantiation via factory method failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: 
Factory method 'servletEndpointRegistrar' threw exception; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'routeControllerEndpoint' defined in class path 
resource 
[org/apache/camel/spring/boot/actuate/endpoint/CamelRouteControllerEndpointAutoConfiguration.class]:
 Unsatisfied dependency expressed through method 'routeControllerEndpoint' 
parameter 0; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'camelContext' defined in class path resource 
[org/apache/camel/spring/boot/CamelAutoConfiguration.class]: Bean instantiation 
via factory method failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.apache.camel.CamelContext]: Factory method 'camelContext' threw exception; 
nested exception is org.apache.camel.RuntimeCamelException: 
org.apache.camel.TypeConverterLoaderException: Failed to load type converters 
because of: Cannot find any type converter classes from the following packages: 
[org.apache.camel.component.elasticsearch.converter] }}

 

 

A possible solution to this is to use FQN class names instead of package name



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to