Spring Boot > 1.5 fails when camel-swagger-java in place

Hi, I tried to update the spring boot web service example to 1.5.2.RELEASE but it fails when camel-swagger-java is in place. ... Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [javax.validation.Validator]: Factory method 'jsr303Validator' threw exception; n

Re: Spring Boot > 1.5 fails when camel-swagger-java in place

You are right I forgot to mention the version... 2.18.3 -- View this message in context: http://camel.465427.n5.nabble.com/Spring-Boot-1-5-fails-when-camel-swagger-java-in-place-tp5797920p5797923.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring Boot > 1.5 fails when camel-swagger-java in place

Hi Zoran, where do I have to put the validation mode setting, property of the pom, application.yml or as an environment variable? I tried all three but I still get the same error. The log ouptut related to the failure is: Exception encountered during context initialization - cancelling refresh a

Rest DSL - specify charset

Hi, is there a way to specify the charset of the response? My service returns characters like ° or ³ and some clients tend to misinterpret these characters if the charset is not specified (UTF-8 in my case). If I (just) specify the bindingMode as Json as follows... restConfiguration().contextPat

Re: VM Queues Disconnected after Karaf Bundle Update

Hi Raul, I am facing the same problem with 2.12.2 ? But it should be fixed since 2.11.0, how can this be? Regards, Thomas -- View this message in context: http://camel.465427.n5.nabble.com/VM-Queues-Disconnected-after-Karaf-Bundle-Update-tp5727205p5745046.html Sent from the Camel - Users mail

Dozer Type Conversion (2.12.2) not working in Karaf

Hi all, I tried to use the Dozer Type Conversion as explained in the documentation in Karaf but without success. I defined a org.apache.camel.converter.dozer.DozerTypeConverterLoader... and a org.apache.camel.converter.dozer.DozerBeanMapperConfiguration

onCompletion has no Exception / CamelExceptionCaught (anymore)

Hi folks, I am working on a monitoring system to trace the traffic handled by camel. >From importance is the failure handling of course. No I facing the problem that there is no Exception information within an onCompletion block accessible. Neither by exchange.getException() nor via the property C

Re: onCompletion has no Exception / CamelExceptionCaught (anymore)

Hi Claus, Perfect CAMEL-9504 addressed and solved my problem Regards, Thomas -- View this message in context: http://camel.465427.n5.nabble.com/onCompletion-has-no-Exception-CamelExceptionCaught-anymore-tp5777544p5777566.html Sent from the Camel - Users mailing list archive at Nabble.com.

Unexpected onCompletion behavior when using direct

I have two routes, an ‘outer route’ that is called from ‘outside’ and an ‘inner route’ that processes some sub tasks. Both routes have individual /onCompletions /(with route scope). Now I am facing the problem, that the /onCompletion /of the ‘inner route’ is only called when the ‘outer route’ fini

Globally set ActiveMQ configuations in Karaf / OSGi or share the connection factory

Hi folks, Is there a way to set configuration of the AMQ component globally? So far I have to include the configurations in every blueprint xml or publish the JmsConfiguration as an OSGi service and then include the reference in every blueprint. This is even more annoying because the JmsConfigurat

Camel 2.17.0 in Karaf 4.0.4 - installing features extremly slow

Hi everyone, I tried to upgrade from Camel 2.16.2 to 2.17.0 but I am facing the problem that installing some features (like camel-jms) in Karaf (4.0.4) tooks ages or even fails. If I switch back to 2.16.2 everything is back to normal. Any idea? Regards, Thomas -- View this message in context

direct-vm in OSGI - how to handle context updates?

Hi folks, I am using direct-vm to link different camel contexts (environment is Karaf 2.3.3 and Camel 2.12.2). Everything works fine until I update one of the routes acting as the direct-vm cosumer. This leads to 'No consumers available ...' exceptions. The problems seems to be the fact, that the

Re: direct-vm in OSGI - how to handle context updates?

Hi Claus, Thank you for your answer. If I add a block it works. But I need the refresh/restart the context in the correct order. In my example route1, route2 and then route3. This works if I do it manually but I have no glue how this could work automatically in production. I deploy and update the

Re: direct-vm in OSGI - how to handle context updates?

Hi Claus, I don't see the problem on side of Karaf, Felix or OSGi at all or how the contexts are deployed. The problem is that in a dynamic environment the direct-vm consumer does not know the producers. Therefore the consumer cannot trigger a restart of the other contexts. Especially if the conte

Re: direct-vm in OSGI - how to handle context updates?

Hi Willem, Thanks for your answer. But what I don't understand, if the producer and consumer are decoupled, why do I have to restart both (or all) contexts at all to get it working. Wouldn't it make more sense to work similar to jms? Or at least be more dynamic. For example use a registry that do

Quartz Component quartz.properties in Karaf

Hi all, I am trying to configure the quartz scheduler of the Quartz Component via the quarzt.properties in Karaf, but I have no glue where to put the file in Karaf? Regards, Thomas -- View this message in context: http://camel.465427.n5.nabble.com/Quartz-Component-quartz-properties-in-Karaf-t