Re: custom consumer doesn't change the delay

2015-09-21 Thread Claus Ibsen
Well its how we do it in camel-mail https://github.com/apache/camel/blob/master/components/camel-mail/src/main/java/org/apache/camel/component/mail/MailEndpoint.java#L59 eg set it on the endpoint. On Tue, Sep 22, 2015 at 7:36 AM, peter_ce wrote: > Hi > > The behavior is still the same in Camel 2

report a possible race issue

2015-09-21 Thread baigd
Hi, Developers of apache/camel, I am writing to report a race issue on use of ConcurrentHashMap. The issue is reported by our tool in an automatic way. Although manually confirmed, it would be a false positive, given we do not know the specification of the program. We would very appreciate if you

Re: setting JMS Priroity 9

2015-09-21 Thread cperi8
Hey Raul Thanks for the reply. I am using IBM MQ/Websphere Message Broker. Here is more detail . Do I need to configure from WMB broker side? In my RouteBuilder am doing this : exchange.getOut.setHeader("JMSPriority",9); exchange.getOut.setHeader("JMSMessageId", 1234); then in the endpoint - I

Re: custom consumer doesn't change the delay

2015-09-21 Thread peter_ce
Hi The behavior is still the same in Camel 2.15.3. -- View this message in context: http://camel.465427.n5.nabble.com/custom-consumer-doesn-t-change-the-delay-tp5771708p5771744.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Closing down for 2.16 release

2015-09-21 Thread Christian Müller
I will try to run some tests and check the new components before you are cutting the release... Best, Christian Am 21.09.2015 16:25 schrieb "Daniel Kulp" : > > I believe things are stabilizing. There are still a bunch of open > JIRA’s, but I think most can be moved to 2.16.1. I’ll try and

Re: Closing down for 2.16 release

2015-09-21 Thread Andrea Cosentino
Every day my signature becomes uglier :-( On Monday, September 21, 2015 5:54 PM, Andrea Cosentino wrote: I was working on Camel-Kubernetes component, but I think I'd never finish for the next monday :-) So I will push on Camel-2.17.x :-) I will try to push some minor commits before

Re: Closing down for 2.16 release

2015-09-21 Thread Andrea Cosentino
I was working on Camel-Kubernetes component, but I think I'd never finish for the next monday :-) So I will push on Camel-2.17.x :-) I will try to push some minor commits before next monday. Thank you Daniel :-) --  Andrea Cosentino   -Apache Camel Committer   Emai

Re: Contributing to the wiki

2015-09-21 Thread Claus Ibsen
Hi When your name is on this page http://people.apache.org/committer-index.html Then create an account on the wiki and let us know your username and post here again. Then we can grant karma. Thanks for helping with the project. On Mon, Sep 21, 2015 at 4:57 PM, Asaf Mesika wrote: > Hi, > > I've

Re: Closing down for 2.16 release

2015-09-21 Thread Claus Ibsen
Sounds like a good plan. On Mon, Sep 21, 2015 at 4:25 PM, Daniel Kulp wrote: > > I believe things are stabilizing. There are still a bunch of open JIRA’s, > but I think most can be moved to 2.16.1. I’ll try and spend some more > time this week looking at some of them. > > In the interes

Contributing to the wiki

2015-09-21 Thread Asaf Mesika
Hi, I've signed and emailed the ICLA to the secretery, in a goal to contribute to the wiki. What do I do next?

Re: custom consumer doesn't change the delay

2015-09-21 Thread Claus Ibsen
Hi I think we fixed a bug in that delay stuff. Can you try with latest release? On Mon, Sep 21, 2015 at 2:46 PM, peter_ce wrote: > Hi > > my custom component won't change the delay for the polling events. The > consumer inherits from ScheduledPollConsumer and sets the delay with > setDelay(). >

Re: Closing down for 2.16 release

2015-09-21 Thread Daniel Kulp
I believe things are stabilizing. There are still a bunch of open JIRA’s, but I think most can be moved to 2.16.1. I’ll try and spend some more time this week looking at some of them. In the interest of trying to get 2.16 out in Q3, I’d be happy to do the build next Monday. (OK, wi

Re: Servlet and REST component integration is not complete

2015-09-21 Thread Sergey Beryozkin
Hi, On 21/09/15 14:50, Claus Ibsen wrote: btw are the other questions about REST I may have missed? All is clear so far, thanks, though I will likely have more questions. FYI, +1 to your comments about not doing all the work in the rest endpoint, I was really referring to a camel-servlet endp

Re: Servlet and REST component integration is not complete

2015-09-21 Thread Claus Ibsen
btw are the other questions about REST I may have missed? Its great to hear that works on supporting it from CXF is in the works. On Mon, Sep 21, 2015 at 3:43 PM, Claus Ibsen wrote: > Hi > > Yes there is no rest content negoation and whatnot in camel-core. That > said if we find in the future a

Re: Servlet and REST component integration is not complete

2015-09-21 Thread Claus Ibsen
Hi Yes there is no rest content negoation and whatnot in camel-core. That said if we find in the future a need for this we can surely add something. But the goal of the rest-dsl was to be that syntax sugar so ppl could do "route like" rest services, and then leave the bulk work to the existing res

Re: Servlet and REST component integration is not complete

2015-09-21 Thread Sergey Beryozkin
Hi Claus - thanks for getting back to this thread. That what I meant, that after the camel-servlet based RESt-DSL consumer is up it does not enforce Accept vs Produces intersection. Cheers, Sergey On 21/09/15 12:02, Claus Ibsen wrote: The rest-dsl is syntax sugar, and passes on the request to

custom consumer doesn't change the delay

2015-09-21 Thread peter_ce
Hi my custom component won't change the delay for the polling events. The consumer inherits from ScheduledPollConsumer and sets the delay with setDelay(). Once Camel (org.apache.camel.impl.EventDrivenConsumerRoute.addServices(List)) creates it, the delay will be set back to default (500ms). Looks

Re: REST DSL Component, Consumer and Endpoint properties as Strings

2015-09-21 Thread Sergey Beryozkin
This is helpful, thanks Cheers, Sergey On 21/09/15 11:55, Claus Ibsen wrote: You can configure complex objects using the lookup notation using #nameOfBean. This is how you would configure Camel endpoints usually. The rest-dsl is for both java and xml and the syntax is for using values that are

Re: HTTP Options request (netty-http, netty4-http)

2015-09-21 Thread Charles Moulliard
Even if the goal was not with first implementations of REST DSL to expose the OPTIONS verb within the DSL, I think that it makes sense to propose it ( https://issues.apache.org/jira/browse/CAMEL-9129) for the following reasons : - The browser will issue OPTIONS requests when CORS is enabled. This i

Re: Servlet and REST component integration is not complete

2015-09-21 Thread Claus Ibsen
The rest-dsl is syntax sugar, and passes on the request to the actual transport, which then does what it care to do. On Tue, Aug 25, 2015 at 7:10 PM, Sergey Beryozkin wrote: > Hi, > Experimenting a bit with a camel-example-servlet-rest-tomcat, > ServletComponent creates a Consumer for RESTCompon

Re: HTTP Options request (netty-http, netty4-http)

2015-09-21 Thread Claus Ibsen
The options was never meant to be exposed in the rest-dsl, when it was created. The options was for the built-in CORS support. On Mon, Sep 14, 2015 at 9:26 PM, Charles Moulliard wrote: > Hi, > > I think that the logic of this test is wrong ( > https://github.com/apache/camel/blob/master/comp

Re: REST DSL Component, Consumer and Endpoint properties as Strings

2015-09-21 Thread Claus Ibsen
You can configure complex objects using the lookup notation using #nameOfBean. This is how you would configure Camel endpoints usually. The rest-dsl is for both java and xml and the syntax is for using values that are possible in both worlds. Its rest configuration is also for simpler and lighter