Re: Exception as warning in Camel 3.4.1

) [?:?], at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?] Kind regards, Remco Schoen > Op 4 sep. 2020, om 10:43 heeft Remco Schoen het > volgende geschreven: > > I upgraded to 3.4.3 and I haven’t seen it since, so I’m guessing this got >

Re: Exception as warning in Camel 3.4.1

I upgraded to 3.4.3 and I haven’t seen it since, so I’m guessing this got fixed somewhere. Greetz, Remco > Op 26 aug. 2020, om 13:12 heeft Remco Schoen het > volgende geschreven: > > Hi, > > I sometimes get this warning, when running my project. It doesn’t end up in >

Exception as warning in Camel 3.4.1

can create an easy test-case. Kind regards, Remco Schoen

Re: Simple language in 3.1.0

At the URL I posted: https://camel.apache.org/components/latest/languages/simple-language.html And Google found it for me… Op 23 apr. 2020, om 16:20 heeft Claus Ibsen mailto:claus.ib...@gmail.com>> het volgende geschreven: On Thu, Apr 23, 2020 at 4:19 PM Remco Schoen mailto

Re: Simple language in 3.1.0

be omitted if the expression is only the token itself.” I’m reading this as it is still allowed, but maybe this has to be removed or it means something different. Kind regards, Remco Schoen > Op 23 apr. 2020, om 16:08 heeft Guillaume Nodet het > volgende geschreven: > > The sy

Simple language in 3.1.0

${body} placeholders for complex expressions where the expression contains constant literals. The $\{ } placeholders can be omitted if the expression is only the token itself.” Should this still work in Camel 3? Kind regards, Remco Schoen P.S. I haven’t had time yet to research the upgrade to Camel

Re: Camel 3.1: dependency vulnerability in camel-main/headersmap

[INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test Il giorno gio 2 apr 2020 alle ore 17:53 Remco Schoen mailto:r.sch...@topdesk.com>> ha scritto: Hi, Not sure if this the correct place for this, but I post it any way. Our vulnerability scanner found a dependency vulnerability in camel-main and more speci

Camel 3.1: dependency vulnerability in camel-main/headersmap

ndency. Kind regards, Remco Schoen

Re: Camel 3.1: camelContext scoped errorHandler

Op 19 mrt. 2020, om 12:45 heeft Claus Ibsen het > volgende geschreven: > > Hi > > adapt to extended camel context and there is a setter for error handler > factory > > On Thu, Mar 19, 2020 at 12:25 PM Remco Schoen wrote: >> >> Hi, >> >> I was

Camel 3.1: camelContext scoped errorHandler

') context.setErrorHandlerBuilder(deadLetterChannelBuilder) context.start() } Is something similar still possible in Camel 3.1? With Spring DSL this is still possible, but I would like to avoid that in my tests. Kind regards, Remco Schoen

Re: Camel 3.1.0: dumping message history and CamelTestSupport

m before method is too late. > > On Fri, Mar 13, 2020 at 3:40 PM Remco Schoen wrote: >> >> Hi, >> >> Before Camel 3.1.0 I was able to dump my complete message history with this >> method: >> >> MessageHelper.dumpMessageHistoryStacktrace(exchan

Camel 3.1.0: dumping message history and CamelTestSupport

Hi, Before Camel 3.1.0 I was able to dump my complete message history with this method: MessageHelper.dumpMessageHistoryStacktrace(exchange, new DefaultExchangeFormatter(), false) According to the change document I try to activate the message history: @Before void init() {

Re: Camel version 3.0.2

e this helps, >> Alex >> >> On Fri, Mar 13, 2020 at 3:16 PM Remco Schoen wrote: >> >>> Hi, >>> >>> As there are a lot of breaking changes for my projects in version 3.1.0, >> I >>> was wondering if there is going to be a version 3.0.2 and if yes, when >> will >>> it be released? >>> >>> Kind regards, >>> >>> Remco Schoen >>

Camel version 3.0.2

Hi, As there are a lot of breaking changes for my projects in version 3.1.0, I was wondering if there is going to be a version 3.0.2 and if yes, when will it be released? Kind regards, Remco Schoen

Re: Camel 3.1.0: error handling changed, route no longer stops

Hi, I raised an issue: https://issues.apache.org/jira/browse/CAMEL-14684 Op 9 mrt. 2020, om 16:17 heeft Guillaume Nodet het volgende geschreven: Would you mind raising a JIRA issue and attaching your test ? I'll have a look at the problem. Le lun. 9 mars 2020 à 15:48, Remco Schoen

Re: Camel 3.1.0: error handling changed, route no longer stops

te").expectedMessageCount(1) getMockEndpoint("mock:nextRoute").expectedMessageCount(0) template.sendBody('direct:start', null) assertMockEndpointsSatisfied() } Regards, Remco Op 9 mrt. 2020, om 15:47 heeft Remco Schoen mailto:r.sch...@topdesk.com>> het volgende ges

Camel 3.1.0: error handling changed, route no longer stops

route stops, but that has changed. Is this correct and should we change our aggregation strategy? I added the strategy and it’s test. Kind regards, Remco Schoen

Re: Camel 3.0.1 - NullPointerException with @BeanInject

31 jan. 2020, om 17:13 heeft Remco Schoen mailto:r.sch...@topdesk.com>> het volgende geschreven: Hi, When testing if I can use Camel 3, I’m getting a NullPointerException when trying to start Camel. Part of the stacktrace: Exception in thread "main" or

Re: Camel 3.0.1 - NullPointerException with @BeanInject

I added a null-check in the method getInjectionBeanValue of the CamelPostProcessorHelper and that seemed to solve it: if (camelContext != null && type.isAssignableFrom(camelContext.getClass())) { return camelContext; } > Op 31 jan. 2020, om 17:13 heeft Remco Schoen het

Camel 3.0.1 - NullPointerException with @BeanInject

Any clue what could be wrong? I’m trying to create a simple test-case. Kind regards, Remco Schoen

Re: Camel 3.0.1 - how to use properties for OTAP?

uish between properties for > testing and production through the propertyPrefix, no, you can't do it > anymore. > > Il giorno ven 31 gen 2020 alle ore 16:57 Remco Schoen > ha scritto: > >> Let me rephrase the question: >> >> So it is no longer possible to distinguish

Re: Camel 3.0.1 - how to use properties for OTAP?

harmful than useful > > Actually the propertyPrefix is set to default and cannot be changed. > > Il giorno ven 31 gen 2020 alle ore 16:52 Remco Schoen > ha scritto: > >> I repeat my question: >> >> Is there a way of doing such a setup in Camel 3? I rather wo

Re: Camel 3.0.1 - how to use properties for OTAP?

been removed. > > https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_properties_component > > Il giorno ven 31 gen 2020 alle ore 16:48 Remco Schoen > ha scritto: > >> Hi, >> >> I was testing to see if I can use Camel 3.0.1 for my work and I found

Camel 3.0.1 - how to use properties for OTAP?

acc.component=jetty:http://0.0.0.0:80 # CAUTION: production setting prod.component=jetty:http://0.0.0.0:80 Is there a way of doing such a setup in Camel 3? I rather wouldn’t like to have multiple properties files. Kind regards, Remco Schoen

Re: Camel with Olingo4 not shutting down

I created an issue for this: https://issues.apache.org/jira/browse/CAMEL-13475?filter=-2 -- Met vriendelijke groet, Remco Schoen Op 29 apr. 2019, om 13:36 heeft Andrea Cosentino mailto:anco...@gmail.com>> het volgende geschreven: Please raise an issue for this one too

Re: Camel with Olingo4 not shutting down

I retested is on version 2.23.2 and I had the same issue there. -- Met vriendelijke groet, Remco Schoen Op 29 apr. 2019, om 10:47 heeft Andrea Cosentino mailto:anco...@gmail.com>> het volgende geschreven: There were a bunch of improvement on 2.22.x branch https://github.com/apache

Re: Problem with Olingo4 and authenticated metadata

I retested is on version 2.23.2 and I had the same issue there. I created an issue for this: https://issues.apache.org/jira/browse/CAMEL-13464 -- Met vriendelijke groet, Remco Schoen Op 29 apr. 2019, om 10:48 heeft Andrea Cosentino mailto:anco...@gmail.com>> het volgende gesc

Re: Camel with Olingo4 not shutting down

Sorry, forgot to add that. I’m using version 2.22.0 at the moment. -- Met vriendelijke groet, Remco Schoen Op 29 apr. 2019, om 10:40 heeft Andrea Cosentino mailto:anco...@gmail.com>> het volgende geschreven: Can you specify the camel version you're using? Il giorno lun 29 apr 2019 al

Re: Problem with Olingo4 and authenticated metadata

Sorry, forgot to add that. I’m using version 2.22.0 at the moment. -- Met vriendelijke groet, Remco Schoen Op 29 apr. 2019, om 10:40 heeft Andrea Cosentino mailto:anco...@gmail.com>> het volgende geschreven: Can you specify what version of Camel are you using? Il giorno lun 29 ap

Camel with Olingo4 not shutting down

) { try { client.close(); } catch (IOException e) { throw new RuntimeException(e); } } } Not sure what should happen when somebody uses their own httpAsyncClientBuilder. Kind regards, Remco Schoen

Problem with Olingo4 and authenticated metadata

.endpointHttpHeaders header for this. But when the component is retrieving the metadata it is ignoring the header and it is not able to authenticate. If I add the headers to the get metadata request it works. Is adding the headers the solution or is there another approach? Kind regards, Remco Schoen

Re: Groovy DSL - expression closures

Hi, I understand :) Maybe an idea to mention on that page, that it is deprecated. -- Met vriendelijke groet, Remco Schoen Op 23 aug. 2017, om 07:33 heeft Claus Ibsen <claus.ib...@gmail.com<mailto:claus.ib...@gmail.com>> het volgende geschreven: Hi The groovy DSL is deprec

Groovy DSL - expression closures

Hi, I’m trying to get processor closures to work as described on: http://camel.apache.org/groovy-dsl.html But when I put the code below in a groovy file, it gives an error. Should this work? Kind regards, Remco Schoen The error: groovy.lang.MissingMethodException: No signature of method

Issue with Rest DSL, Jetty and Basic authentication

to the Jetty server. If it has been added, it can be found when re-adding the security handler. How can I solve this error? Kind regards, Remco Schoen camel-context.xml: http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-ins

Re: No HTTP response when using onException with BeanValidationException

erver, so the headers were already changed before the exception. -- Met vriendelijke groet, Remco Schoen Op 14 okt. 2016, om 16:36 heeft Remco Schoen <r.sch...@topdesk.com<mailto:r.sch...@topdesk.com>> het volgende geschreven: Hi, I’m trying to use the REST DSL and do validatio

No HTTP response when using onException with BeanValidationException

${exception.message} But when I use the Swagger UI to send a message to my endpoint, I get no body or HTTP response code. For other exceptions this approach works. Should this work with this exception? I’m using version 2.17.3 Kind regards, Remco Schoen