Re: "Gave up waiting for BlueprintContainer" when using camel-test-blueprint
Hi, Typically it happens on CamelBlueprintTestSupport when you omit some OSGi dependencies in pom.xml: It's not just Maven dependencies but also OSGi bundle imports/exports. Typically a successful camel blueprint test has a felix maven-bundle-plugin configuration and the import/export packages declarations like these: https://github.com/apache/camel/blob/master/parent/pom.xml#L5287-L5334 https://github.com/apache/camel/blob/master/examples/camel-example-servlet-rest-blueprint/pom.xml#L40-L45 Hope this helps. On Tue, Feb 13, 2018 at 9:41 AM, Harrison Tarr wrote: > Hi, > > I just heard about "camel-test-blueprint" today and I started using it. I > was able to get a feel for it by using a contrived Camel route in a > blueprint.xml and everything worked as expected. I'm now trying to test > "real" camel routes in my products blueprint.xml, but I'm getting a > RuntimeException: "Gave up waiting for BlueprintContainer". Any ideas what > causes that? I'm at a loss, even after Google. > > Best Regards, > > Harrison Tarr >
"Gave up waiting for BlueprintContainer" when using camel-test-blueprint
Hi, I just heard about "camel-test-blueprint" today and I started using it. I was able to get a feel for it by using a contrived Camel route in a blueprint.xml and everything worked as expected. I'm now trying to test "real" camel routes in my products blueprint.xml, but I'm getting a RuntimeException: "Gave up waiting for BlueprintContainer". Any ideas what causes that? I'm at a loss, even after Google. Best Regards, Harrison Tarr
Re: JMS: override Camel header type conversions?
Same as Quinn, I would vote for the ISO-8601 standard. However, I would consider delaying the change to camel 3.0 or making it optional. On Mon, Feb 12, 2018 at 9:50 PM, Quinn Stevenson < qu...@pronoia-solutions.com> wrote: > If it’s going to change, I would vote for the ISO-8601 format - that’s > what I use for all my timestamps in logs and such. > > > > On Feb 12, 2018, at 12:07 PM, Claus Ibsen wrote: > > > > Hi > > > > Maybe it sounds like a better idea to use a iso-xxx date to be > > consistent, instead of a toString that may be OS locale dependent etc. > > > > Or it could store the value as a long value of the epoc. > > > > > > > > > > On Mon, Feb 12, 2018 at 12:19 PM, Quinn Stevenson > > wrote: > >> Sorry - ignore that. That feature is used to customize the mapping of > the key names - not the values. > >> > >> The only way I can think of right off hand is to add you’re own bean > that manipulates the header values before you send them. > >> > >> > >>> On Feb 12, 2018, at 10:14 AM, Quinn Stevenson < > qu...@pronoia-solutions.com> wrote: > >>> > >>> You can provide your own implementation using the jmsKeyFormatStrategy > URI Option. > >>> > >>> > >>> > On Feb 12, 2018, at 8:34 AM, Probert, Matt < > matt.prob...@metoffice.gov.uk> wrote: > > When messages are produced to ActiveMQ, Camel JmsBinding converts > java.util.Date message headers to string via Date.toString(). > > I want to override the conversion, to give IS0 8601 strings. > > Is there a way to inject a custom JmsBinding to do it? Or some other > standard way? I don't want to modify existing route definitions, if > possible. > > I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. > Routes are defined in the spring XML DSL. > Cheers, > Matt > >>> > >> > > > > > > > > -- > > Claus Ibsen > > - > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > >
RE: JMS: override Camel header type conversions?
Thanks Claus, Thanks Quinn, I prefer an ISO string, because it's less ambiguous than an epoch-millisecond type value. But a way to have it configurable would be even better. -Original Message- From: Quinn Stevenson [mailto:qu...@pronoia-solutions.com] Sent: 12 February 2018 20:51 To: users@camel.apache.org Subject: Re: JMS: override Camel header type conversions? If it’s going to change, I would vote for the ISO-8601 format - that’s what I use for all my timestamps in logs and such. > On Feb 12, 2018, at 12:07 PM, Claus Ibsen wrote: > > Hi > > Maybe it sounds like a better idea to use a iso-xxx date to be > consistent, instead of a toString that may be OS locale dependent etc. > > Or it could store the value as a long value of the epoc. > > > > > On Mon, Feb 12, 2018 at 12:19 PM, Quinn Stevenson > wrote: >> Sorry - ignore that. That feature is used to customize the mapping of the >> key names - not the values. >> >> The only way I can think of right off hand is to add you’re own bean that >> manipulates the header values before you send them. >> >> >>> On Feb 12, 2018, at 10:14 AM, Quinn Stevenson >>> wrote: >>> >>> You can provide your own implementation using the jmsKeyFormatStrategy URI >>> Option. >>> >>> >>> On Feb 12, 2018, at 8:34 AM, Probert, Matt wrote: When messages are produced to ActiveMQ, Camel JmsBinding converts java.util.Date message headers to string via Date.toString(). I want to override the conversion, to give IS0 8601 strings. Is there a way to inject a custom JmsBinding to do it? Or some other standard way? I don't want to modify existing route definitions, if possible. I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes are defined in the spring XML DSL. Cheers, Matt >>> >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: JMS: override Camel header type conversions?
If it’s going to change, I would vote for the ISO-8601 format - that’s what I use for all my timestamps in logs and such. > On Feb 12, 2018, at 12:07 PM, Claus Ibsen wrote: > > Hi > > Maybe it sounds like a better idea to use a iso-xxx date to be > consistent, instead of a toString that may be OS locale dependent etc. > > Or it could store the value as a long value of the epoc. > > > > > On Mon, Feb 12, 2018 at 12:19 PM, Quinn Stevenson > wrote: >> Sorry - ignore that. That feature is used to customize the mapping of the >> key names - not the values. >> >> The only way I can think of right off hand is to add you’re own bean that >> manipulates the header values before you send them. >> >> >>> On Feb 12, 2018, at 10:14 AM, Quinn Stevenson >>> wrote: >>> >>> You can provide your own implementation using the jmsKeyFormatStrategy URI >>> Option. >>> >>> >>> On Feb 12, 2018, at 8:34 AM, Probert, Matt wrote: When messages are produced to ActiveMQ, Camel JmsBinding converts java.util.Date message headers to string via Date.toString(). I want to override the conversion, to give IS0 8601 strings. Is there a way to inject a custom JmsBinding to do it? Or some other standard way? I don't want to modify existing route definitions, if possible. I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes are defined in the spring XML DSL. Cheers, Matt >>> >> > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: JMS: override Camel header type conversions?
Hi Maybe it sounds like a better idea to use a iso-xxx date to be consistent, instead of a toString that may be OS locale dependent etc. Or it could store the value as a long value of the epoc. On Mon, Feb 12, 2018 at 12:19 PM, Quinn Stevenson wrote: > Sorry - ignore that. That feature is used to customize the mapping of the > key names - not the values. > > The only way I can think of right off hand is to add you’re own bean that > manipulates the header values before you send them. > > >> On Feb 12, 2018, at 10:14 AM, Quinn Stevenson >> wrote: >> >> You can provide your own implementation using the jmsKeyFormatStrategy URI >> Option. >> >> >> >>> On Feb 12, 2018, at 8:34 AM, Probert, Matt >>> wrote: >>> >>> When messages are produced to ActiveMQ, Camel JmsBinding converts >>> java.util.Date message headers to string via Date.toString(). >>> >>> I want to override the conversion, to give IS0 8601 strings. >>> >>> Is there a way to inject a custom JmsBinding to do it? Or some other >>> standard way? I don't want to modify existing route definitions, if >>> possible. >>> >>> I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. >>> Routes are defined in the spring XML DSL. >>> Cheers, >>> Matt >> > -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
RE: JMS: override Camel header type conversions?
Thanks Quinn, I had looked at jmsKeyFormatStrategy, and came to the same conclusion. I guess I have to modify my routes, like you say. -Original Message- From: Quinn Stevenson [mailto:qu...@pronoia-solutions.com] Sent: 12 February 2018 17:20 To: users@camel.apache.org Subject: Re: JMS: override Camel header type conversions? Sorry - ignore that. That feature is used to customize the mapping of the key names - not the values. The only way I can think of right off hand is to add you’re own bean that manipulates the header values before you send them. > On Feb 12, 2018, at 10:14 AM, Quinn Stevenson > wrote: > > You can provide your own implementation using the jmsKeyFormatStrategy URI > Option. > > > >> On Feb 12, 2018, at 8:34 AM, Probert, Matt >> wrote: >> >> When messages are produced to ActiveMQ, Camel JmsBinding converts >> java.util.Date message headers to string via Date.toString(). >> >> I want to override the conversion, to give IS0 8601 strings. >> >> Is there a way to inject a custom JmsBinding to do it? Or some other >> standard way? I don't want to modify existing route definitions, if possible. >> >> I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes >> are defined in the spring XML DSL. >> Cheers, >> Matt >
Re: JMS: override Camel header type conversions?
Sorry - ignore that. That feature is used to customize the mapping of the key names - not the values. The only way I can think of right off hand is to add you’re own bean that manipulates the header values before you send them. > On Feb 12, 2018, at 10:14 AM, Quinn Stevenson > wrote: > > You can provide your own implementation using the jmsKeyFormatStrategy URI > Option. > > > >> On Feb 12, 2018, at 8:34 AM, Probert, Matt >> wrote: >> >> When messages are produced to ActiveMQ, Camel JmsBinding converts >> java.util.Date message headers to string via Date.toString(). >> >> I want to override the conversion, to give IS0 8601 strings. >> >> Is there a way to inject a custom JmsBinding to do it? Or some other >> standard way? I don't want to modify existing route definitions, if possible. >> >> I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes >> are defined in the spring XML DSL. >> Cheers, >> Matt >
Re: JMS: override Camel header type conversions?
You can provide your own implementation using the jmsKeyFormatStrategy URI Option. > On Feb 12, 2018, at 8:34 AM, Probert, Matt > wrote: > > When messages are produced to ActiveMQ, Camel JmsBinding converts > java.util.Date message headers to string via Date.toString(). > > I want to override the conversion, to give IS0 8601 strings. > > Is there a way to inject a custom JmsBinding to do it? Or some other standard > way? I don't want to modify existing route definitions, if possible. > > I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes > are defined in the spring XML DSL. > Cheers, > Matt
JMS: override Camel header type conversions?
When messages are produced to ActiveMQ, Camel JmsBinding converts java.util.Date message headers to string via Date.toString(). I want to override the conversion, to give IS0 8601 strings. Is there a way to inject a custom JmsBinding to do it? Or some other standard way? I don't want to modify existing route definitions, if possible. I'm using the camel-activemq component, Camel 2.14.1, ActiveMQ 5.7.0. Routes are defined in the spring XML DSL. Cheers, Matt
