from:"Henryk Konsek \(JIRA\)"

[jira] [Resolved] (CAMEL-9385) Create Apache Spark component

2015-12-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9385.
--
Resolution: Fixed

Done.

> Create Apache Spark component
> -
>
> Key: CAMEL-9385
> URL: https://issues.apache.org/jira/browse/CAMEL-9385
> Project: Camel
>  Issue Type: New Feature
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> As a part of the the IoT project I'm working on, I have created a Spark 
> component (1) to make it easier to handle analytics requests from devices. I 
> would like to donate this code to the ASF Camel and extend it here, as I 
> guess that there would be many people interested in using Spark from Camel.
> The URI looks like {{spark:rdd/rddName/rddCallback}} or 
> {{spark:dataframe/frameName/frameCallback}} depending if you would like to 
> work with RDDs or DataFrames.
> The idea here is that Camel route acts as a driver application. You specify 
> RDD/DataFrames definitions (and callbacks to act against those) in a registry 
> (for example as Spring beans or OSGi services). Then you send a parameters 
> for the computations as a body of a message.
> For example in Spring Boot you specify RDD+callback as:
> {code}
> @Bean
> JavaRDD myRdd(SparkContext sparkContext) {
>   return sparkContext.textFile("foo.txt");
> }
> @Bean
> class MyAnalytics {
>   @RddCallback
>   long countLines(JavaRDD textFile, long argument) {
>  return rdd.count() * argument;
>   }
> }
> {code}
> Then you ask for the results of computations:
> {code}
> long results = producerTemplate.requestBody("spark:rdd/myRdd/MyAnalytics", 
> 10, long.class);
> {code}
> Such setup is extremely useful for bridging Spark computations via different 
> transports.
> (1) https://github.com/rhiot/rhiot/tree/master/components/camel-spark



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9244) camel-paho - Endpoint must implement publishing of retained messages option

2015-12-11 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15053481#comment-15053481
 ] 

Henryk Konsek commented on CAMEL-9244:
--

[~gautric] Would you like to handle this or should I do it?

> camel-paho - Endpoint must implement publishing of retained messages option
> ---
>
> Key: CAMEL-9244
> URL: https://issues.apache.org/jira/browse/CAMEL-9244
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Affects Versions: 2.16.0
>Reporter: Jaume Teixi
>Assignee: Greg A.
>
> Currently PahoEndpoint allows to set the QoS option.
> But the boolean retained is a basic MQTT protocol feature that should be 
> implemented.
> Like in the Paho publish method:
> org.eclipse.paho.client.mqttv3.MqttClient
> #publish(String topic, byte[] payload, int qos, boolean retained) 
> Additionally it would be nice to have the MqttConnectOptions of setWill as 
> also "Last Will and Testament" (LWT) is a basic protocol feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9385) Create Apache Spark component

2015-12-07 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044565#comment-15044565
 ] 

Henryk Konsek commented on CAMEL-9385:
--

Will do. I'm working now on documentation page for component, so I will add 
annotations docs as well.

> Create Apache Spark component
> -
>
> Key: CAMEL-9385
> URL: https://issues.apache.org/jira/browse/CAMEL-9385
> Project: Camel
>  Issue Type: New Feature
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> As a part of the the IoT project I'm working on, I have created a Spark 
> component (1) to make it easier to handle analytics requests from devices. I 
> would like to donate this code to the ASF Camel and extend it here, as I 
> guess that there would be many people interested in using Spark from Camel.
> The URI looks like {{spark:rdd/rddName/rddCallback}} or 
> {{spark:dataframe/frameName/frameCallback}} depending if you would like to 
> work with RDDs or DataFrames.
> The idea here is that Camel route acts as a driver application. You specify 
> RDD/DataFrames definitions (and callbacks to act against those) in a registry 
> (for example as Spring beans or OSGi services). Then you send a parameters 
> for the computations as a body of a message.
> For example in Spring Boot you specify RDD+callback as:
> {code}
> @Bean
> JavaRDD myRdd(SparkContext sparkContext) {
>   return sparkContext.textFile("foo.txt");
> }
> @Bean
> class MyAnalytics {
>   @RddCallback
>   long countLines(JavaRDD textFile, long argument) {
>  return rdd.count() * argument;
>   }
> }
> {code}
> Then you ask for the results of computations:
> {code}
> long results = producerTemplate.requestBody("spark:rdd/myRdd/MyAnalytics", 
> 10, long.class);
> {code}
> Such setup is extremely useful for bridging Spark computations via different 
> transports.
> (1) https://github.com/rhiot/rhiot/tree/master/components/camel-spark



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9385) Create Apache Spark component

2015-12-04 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15041422#comment-15041422
 ] 

Henryk Konsek commented on CAMEL-9385:
--

Initial version committed in b46392c25bd517cbb7d04e6dd7611d1634378a13.

> Create Apache Spark component
> -
>
> Key: CAMEL-9385
> URL: https://issues.apache.org/jira/browse/CAMEL-9385
> Project: Camel
>  Issue Type: New Feature
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> As a part of the the IoT project I'm working on, I have created a Spark 
> component (1) to make it easier to handle analytics requests from devices. I 
> would like to donate this code to the ASF Camel and extend it here, as I 
> guess that there would be many people interested in using Spark from Camel.
> The URI looks like {{spark:rdd/rddName/rddCallback}} or 
> {{spark:dataframe/frameName/frameCallback}} depending if you would like to 
> work with RDDs or DataFrames.
> The idea here is that Camel route acts as a driver application. You specify 
> RDD/DataFrames definitions (and callbacks to act against those) in a registry 
> (for example as Spring beans or OSGi services). Then you send a parameters 
> for the computations as a body of a message.
> For example in Spring Boot you specify RDD+callback as:
> {code}
> @Bean
> JavaRDD myRdd(SparkContext sparkContext) {
>   return sparkContext.textFile("foo.txt");
> }
> @Bean
> class MyAnalytics {
>   @RddCallback
>   long countLines(JavaRDD textFile, long argument) {
>  return rdd.count() * argument;
>   }
> }
> {code}
> Then you ask for the results of computations:
> {code}
> long results = producerTemplate.requestBody("spark:rdd/myRdd/MyAnalytics", 
> 10, long.class);
> {code}
> Such setup is extremely useful for bridging Spark computations via different 
> transports.
> (1) https://github.com/rhiot/rhiot/tree/master/components/camel-spark



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9387) Camel AMQP hardening

2015-12-03 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9387:


 Summary: Camel AMQP hardening
 Key: CAMEL-9387
 URL: https://issues.apache.org/jira/browse/CAMEL-9387
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


I'd like to have more unit tests of AMQP component. The same applies for 
documentation. I'd would also add a {{AMQPConnectionDetails}} class which could 
be used auto-configure AMQP connections from the registry level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9387) Camel AMQP hardening

2015-12-03 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9387.
--
Resolution: Fixed

Done, as we love AMQP. <3

> Camel AMQP hardening
> 
>
> Key: CAMEL-9387
> URL: https://issues.apache.org/jira/browse/CAMEL-9387
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> I'd like to have more unit tests of AMQP component. The same applies for 
> documentation. I'd would also add a {{AMQPConnectionDetails}} class which 
> could be used auto-configure AMQP connections from the registry level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9388) Provide properties-based AMQP connection discovery

2015-12-03 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9388:


 Summary: Provide properties-based AMQP connection discovery
 Key: CAMEL-9388
 URL: https://issues.apache.org/jira/browse/CAMEL-9388
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


I'd love to have an option to automatically read AMQP connection parameters 
from Camel properties. So for example in Spring Boot I can create a bean like:

{code}
@Bean
AMQPConnectionDetails amqpConnection() {
  return new AMQPConnectionDetails.discoverAMQP();
}
{code}

{{AMQPConnectionDetails.discoverAMQP}} should try to read its parameters from a 
Camel properties. So if you set {{AMQP_SERVICE_HOST}} property, Camel will use 
that value. 

I propose to follow Kubernetes service convention for properties. As as result 
the snippet above deployed into Kubernetes environment will work out of the 
box, as {{AMQP_SERVICE_HOST}} and {{AMQP_SERVICE_PORT}} will be provided by 
Kubernetes ENV variables.

You can still rely on the plain good old manual configuration, but this option 
will be especially interesting for convention-over-configuration freaks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9388) Provide properties-based AMQP connection discovery

2015-12-03 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9388.
--
Resolution: Fixed

Fixed in 2dd2d4147de61fc309d66cc0ff5923e93a28951f.

> Provide properties-based AMQP connection discovery
> --
>
> Key: CAMEL-9388
> URL: https://issues.apache.org/jira/browse/CAMEL-9388
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> I'd love to have an option to automatically read AMQP connection parameters 
> from Camel properties. So for example in Spring Boot I can create a bean like:
> {code}
> @Bean
> AMQPConnectionDetails amqpConnection() {
>   return new AMQPConnectionDetails.discoverAMQP();
> }
> {code}
> {{AMQPConnectionDetails.discoverAMQP}} should try to read its parameters from 
> a Camel properties. So if you set {{AMQP_SERVICE_HOST}} property, Camel will 
> use that value. 
> I propose to follow Kubernetes service convention for properties. As as 
> result the snippet above deployed into Kubernetes environment will work out 
> of the box, as {{AMQP_SERVICE_HOST}} and {{AMQP_SERVICE_PORT}} will be 
> provided by Kubernetes ENV variables.
> You can still rely on the plain good old manual configuration, but this 
> option will be especially interesting for convention-over-configuration 
> freaks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9381) Upgrade camel-amqp to the latest qpid-jms-client

2015-12-01 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9381.
--
Resolution: Fixed

Fixed in 4997c2e929d11a1e45fbaaaff3c9cbf6cfbeea08.

> Upgrade camel-amqp to the latest qpid-jms-client
> 
>
> Key: CAMEL-9381
> URL: https://issues.apache.org/jira/browse/CAMEL-9381
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.16.1
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> We should upgrade camel-amqp to use the latest qpid-jms-client. That would 
> mean that we should also drop support for AMQP < 1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9381) Upgrade camel-amqp to the latest qpid-jms-client

2015-12-01 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9381:


 Summary: Upgrade camel-amqp to the latest qpid-jms-client
 Key: CAMEL-9381
 URL: https://issues.apache.org/jira/browse/CAMEL-9381
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.16.1
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


We should upgrade camel-amqp to use the latest qpid-jms-client. That would mean 
that we should also drop support for AMQP < 1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9357) KuraRouter should provide default routes configuration

2015-11-24 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9357:


 Summary: KuraRouter should provide default routes configuration
 Key: CAMEL-9357
 URL: https://issues.apache.org/jira/browse/CAMEL-9357
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.16.0
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


{{KuraRouter}} can be configured via XML and OSGi Configuration Admin. In such 
cases there is no need to implement {{configure()}} method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9357) KuraRouter should provide default routes configuration

2015-11-24 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9357.
--
Resolution: Fixed

Fixed in f13b8851c61e6a08405903b9608d3ef0994af53b.

> KuraRouter should provide default routes configuration
> --
>
> Key: CAMEL-9357
> URL: https://issues.apache.org/jira/browse/CAMEL-9357
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> {{KuraRouter}} can be configured via XML and OSGi Configuration Admin. In 
> such cases there is no need to implement {{configure()}} method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9351) Kura router should offer SCR programming model

2015-11-23 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9351:


 Summary: Kura router should offer SCR programming model
 Key: CAMEL-9351
 URL: https://issues.apache.org/jira/browse/CAMEL-9351
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.16.0
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


Currently {{KuraRouter}} offers only {{BundleActivator}} programming model. As 
Kura promotes SCR for managable objects, {{KuraRouter}} should be easily 
deployed as SCR as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9351) Kura router should offer SCR programming model

2015-11-23 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9351.
--
Resolution: Fixed

Fixed in b914c04ccfb0a16020bd4eb0396d51a08804eaa7. Added {{activate}} and 
{{deactivate}} SCR-friendly methods.

> Kura router should offer SCR programming model
> --
>
> Key: CAMEL-9351
> URL: https://issues.apache.org/jira/browse/CAMEL-9351
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Currently {{KuraRouter}} offers only {{BundleActivator}} programming model. 
> As Kura promotes SCR for managable objects, {{KuraRouter}} should be easily 
> deployed as SCR as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9333) KuraRouter should try to load XML routes from ConfigAdmin

2015-11-17 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9333.
--
Resolution: Fixed

Done in 5068678c43695ed3811b4c1f2edea8f0b2b0a59c.

> KuraRouter should try to load XML routes from ConfigAdmin
> -
>
> Key: CAMEL-9333
> URL: https://issues.apache.org/jira/browse/CAMEL-9333
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> {{KuraRouter}} should try to read XML routes definition from ConfigAdmin when 
> starting. That would allow to modify the routing rules at runtime with a text 
> editor only or using the MQTT updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9333) KuraRouter should try to load XML routes from ConfigAdmin

2015-11-17 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9333:


 Summary: KuraRouter should try to load XML routes from ConfigAdmin
 Key: CAMEL-9333
 URL: https://issues.apache.org/jira/browse/CAMEL-9333
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.16.0
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


{{KuraRouter}} should try to read XML routes definition from ConfigAdmin when 
starting. That would allow to modify the routing rules at runtime with a text 
editor only or using the MQTT updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9328) KuraRouter should provide required and option service resolvers

2015-11-16 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9328:


 Summary: KuraRouter should provide required and option service 
resolvers
 Key: CAMEL-9328
 URL: https://issues.apache.org/jira/browse/CAMEL-9328
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


Current {{service(Class)}} method returns NPE for OSGi services not available 
in Kura. We should provide two methods instead:

- {{service(Class)}}
- {{requiredService(Class)}}

Where the first method can return null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9329) Kura router should provide OSGi compendium services

2015-11-16 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9329:


 Summary: Kura router should provide OSGi compendium services
 Key: CAMEL-9329
 URL: https://issues.apache.org/jira/browse/CAMEL-9329
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.16.0
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


For the current version end user has to provide an OSGi compendium dependency 
in the proper version in the client project. It is annoying and error prone 
process of guessing the right version, so we should import it on the behalf of 
the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9329) Kura router should provide OSGi compendium services

2015-11-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9329.
--
Resolution: Fixed

> Kura router should provide OSGi compendium services
> ---
>
> Key: CAMEL-9329
> URL: https://issues.apache.org/jira/browse/CAMEL-9329
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> For the current version end user has to provide an OSGi compendium dependency 
> in the proper version in the client project. It is annoying and error prone 
> process of guessing the right version, so we should import it on the behalf 
> of the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9329) Kura router should provide OSGi compendium services

2015-11-16 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006383#comment-15006383
 ] 

Henryk Konsek commented on CAMEL-9329:
--

Fixed in dc0b730f68ece9d593fcd6f3c65d146f9e05c31f.

> Kura router should provide OSGi compendium services
> ---
>
> Key: CAMEL-9329
> URL: https://issues.apache.org/jira/browse/CAMEL-9329
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> For the current version end user has to provide an OSGi compendium dependency 
> in the proper version in the client project. It is annoying and error prone 
> process of guessing the right version, so we should import it on the behalf 
> of the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9328) KuraRouter should provide required and option service resolvers

2015-11-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9328:
-
Affects Version/s: 2.16.0

> KuraRouter should provide required and option service resolvers
> ---
>
> Key: CAMEL-9328
> URL: https://issues.apache.org/jira/browse/CAMEL-9328
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Current {{service(Class)}} method returns NPE for OSGi services not available 
> in Kura. We should provide two methods instead:
> - {{service(Class)}}
> - {{requiredService(Class)}}
> Where the first method can return null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9328) KuraRouter should provide required and option service resolvers

2015-11-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9328.
--
Resolution: Fixed

Fixed in 005df4cb73063d19ae11e79a4106ba30c235f24c.

> KuraRouter should provide required and option service resolvers
> ---
>
> Key: CAMEL-9328
> URL: https://issues.apache.org/jira/browse/CAMEL-9328
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Current {{service(Class)}} method returns NPE for OSGi services not available 
> in Kura. We should provide two methods instead:
> - {{service(Class)}}
> - {{requiredService(Class)}}
> Where the first method can return null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9314) Improve error logging in Kura router

2015-11-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9314:
-
Fix Version/s: (was: 2.16.1)
   2.17.0

> Improve error logging in Kura router
> 
>
> Key: CAMEL-9314
> URL: https://issues.apache.org/jira/browse/CAMEL-9314
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Kura console doesn't print (or log) a stacktrace if exception is thrown in 
> {{KuraRouter#start()}} method. It makes debugging Kura module really 
> difficult.
> We should intercept the exception thrown by the {{KuraRouter#start()}} and 
> log these on STDERR and to Kura logger before we let it propagate to the OSGi 
> framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9314) Improve error logging in Kura router

2015-11-12 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9314:


 Summary: Improve error logging in Kura router
 Key: CAMEL-9314
 URL: https://issues.apache.org/jira/browse/CAMEL-9314
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.16.0
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.1


Kura console doesn't print (or log) a stacktrace if exception is thrown in 
{{KuraRouter#start()}} method. It makes debugging Kura module really difficult.

We should intercept the exception thrown by the {{KuraRouter#start()}} and log 
these on STDERR and to Kura logger before we let it propagate to the OSGi 
framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9315) KuraRouter should provide consumer template

2015-11-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9315:
-
Affects Version/s: 2.16.0
Fix Version/s: 2.17.0
  Description: {{KuraRouter}} should provide {{ConsumerTemplate}} 
instance.

> KuraRouter should provide consumer template
> ---
>
> Key: CAMEL-9315
> URL: https://issues.apache.org/jira/browse/CAMEL-9315
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> {{KuraRouter}} should provide {{ConsumerTemplate}} instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9314) Improve error logging in Kura router

2015-11-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9314.
--
Resolution: Fixed

Fixed in 02e3bc66bcbfef8b46a4c1e24f14af657d8210f5.

> Improve error logging in Kura router
> 
>
> Key: CAMEL-9314
> URL: https://issues.apache.org/jira/browse/CAMEL-9314
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Kura console doesn't print (or log) a stacktrace if exception is thrown in 
> {{KuraRouter#start()}} method. It makes debugging Kura module really 
> difficult.
> We should intercept the exception thrown by the {{KuraRouter#start()}} and 
> log these on STDERR and to Kura logger before we let it propagate to the OSGi 
> framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9315) KuraRouter should provide consumer template

2015-11-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9315.
--
Resolution: Fixed

Fixed in d16c52f5820c162be78625c65735a743cf76546e.

> KuraRouter should provide consumer template
> ---
>
> Key: CAMEL-9315
> URL: https://issues.apache.org/jira/browse/CAMEL-9315
> Project: Camel
>  Issue Type: Improvement
>Affects Versions: 2.16.0
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> {{KuraRouter}} should provide {{ConsumerTemplate}} instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9315) KuraRouter should provide consumer template

2015-11-12 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9315:


 Summary: KuraRouter should provide consumer template
 Key: CAMEL-9315
 URL: https://issues.apache.org/jira/browse/CAMEL-9315
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9256) Paho file persistence store should be configurable

2015-10-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9256:


 Summary: Paho file persistence store should be configurable
 Key: CAMEL-9256
 URL: https://issues.apache.org/jira/browse/CAMEL-9256
 Project: Camel
  Issue Type: Improvement
  Components: camel-paho
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0, 2.16.1


In a current version of Paho, a current directory is used as a based for the 
file persistence. This should be configurable, like:

{code}
from("paho:topic?persistence=file=/var/mqtt")...
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9245) camel-paho - Endpoint should allow a flexible naming.

2015-10-25 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973434#comment-14973434
 ] 

Henryk Konsek commented on CAMEL-9245:
--

Oh shit! Did I really commit that? What was on my mind to assume fixed 
component name? :|

Anyway - I have fixed that in 2.17.0 (1) and 2.16.1 (2).

Thanks for reporting (and sorry for a stupid mistake)! 

(1) 14e9236aca9e1cd93f180158767d7e102257f1b6
(2) e791fc27756fddce2eaa759c86250c8c5e7f9a0f

> camel-paho - Endpoint should allow a flexible naming.
> -
>
> Key: CAMEL-9245
> URL: https://issues.apache.org/jira/browse/CAMEL-9245
> Project: Camel
>  Issue Type: Bug
>  Components: camel-paho
>Affects Versions: 2.16.0
>Reporter: Jaume Teixi
>Priority: Minor
> Fix For: 2.17.0, 2.16.1
>
>
> If endpoint doesn't match exactly paho: it fails to publish to the correct 
> topic.
> Once should be able in Spring to @Autowired two different PahoComponent 
> pointing to different Application Context defined PahoComponent bean id'S.
> Currently if bean id is not named exactly paho it fails to publish to the 
> correct topic and for example instead of input/1 publishes to t://input/1 
> when id is mypaho instead of paho



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9245) camel-paho - Endpoint should allow a flexible naming.

2015-10-25 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973436#comment-14973436
 ] 

Henryk Konsek commented on CAMEL-9245:
--

As a workaround hack for the older versions you can also use the component name 
with the length == 4.

> camel-paho - Endpoint should allow a flexible naming.
> -
>
> Key: CAMEL-9245
> URL: https://issues.apache.org/jira/browse/CAMEL-9245
> Project: Camel
>  Issue Type: Bug
>  Components: camel-paho
>Affects Versions: 2.16.0
>Reporter: Jaume Teixi
>Priority: Minor
> Fix For: 2.17.0, 2.16.1
>
>
> If endpoint doesn't match exactly paho: it fails to publish to the correct 
> topic.
> Once should be able in Spring to @Autowired two different PahoComponent 
> pointing to different Application Context defined PahoComponent bean id'S.
> Currently if bean id is not named exactly paho it fails to publish to the 
> correct topic and for example instead of input/1 publishes to t://input/1 
> when id is mypaho instead of paho



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9245) camel-paho - Endpoint should allow a flexible naming.

2015-10-23 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970821#comment-14970821
 ] 

Henryk Konsek commented on CAMEL-9245:
--

Actually publishing to {{input/2}} is what I would expect to happen. You are 
sending a message to the {{input/2}}, so this is published to {{input/2}} :) . 
BTW a component naming is handled by the Camel Core and is outside of the scope 
of the component.

Are you sure it behaves wrong?

> camel-paho - Endpoint should allow a flexible naming.
> -
>
> Key: CAMEL-9245
> URL: https://issues.apache.org/jira/browse/CAMEL-9245
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-paho
>Reporter: Jaume Teixi
>Priority: Minor
>
> If endpoint doesn't match exactly paho: it fails to publish to the correct 
> topic.
> Once should be able in Spring to @Autowired two different PahoComponent 
> pointing to different Application Context defined PahoComponent bean id'S.
> Currently if bean id is not named exactly paho it fails to publish to the 
> correct topic and for example instead of input/1 publishes to t://input/1 
> when id is mypaho instead of paho



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9204) Provide AMQP component factory method for AMQP 1.0

2015-10-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9204:
-
Fix Version/s: 2.16.1

> Provide AMQP component factory method for AMQP 1.0
> --
>
> Key: CAMEL-9204
> URL: https://issues.apache.org/jira/browse/CAMEL-9204
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0, 2.16.1
>
>
> Currently our documentation says that we should configure topic prefix when 
> working with AMQP 1.0.
> {code}
>  >
>
>   class="org.apache.qpid.amqp_1_0.jms.impl.ConnectionFactoryImpl" 
> factory-method="createFromURL">
> value="amqp://localhost:5672" />
>  
>   
>
>
> {code}
> We should provide factory method which creates pre-configured component that 
> can be used with AMQP 1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9203) camel-amqp should provide qpid dependencies

2015-10-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9203.
--
Resolution: Fixed

Fixed in 015532438780c84fa46cb8e9bc9b353662177712.

> camel-amqp should provide qpid dependencies
> ---
>
> Key: CAMEL-9203
> URL: https://issues.apache.org/jira/browse/CAMEL-9203
> Project: Camel
>  Issue Type: Bug
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Currently Qpid dependencies are marked as optional:
> {code}
> 
>   org.apache.qpid
>   qpid-amqp-1-0-client-jms
>   ${qpid-version}
>   true
> 
> 
> org.apache.qpid
> qpid-client
> ${qpid-version}
> true
> 
> {code}
> Those should not be optional, as the component is unusable without those two 
> jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9204) Provide AMQP component factory method for AMQP 1.0

2015-10-09 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9204:


 Summary: Provide AMQP component factory method for AMQP 1.0
 Key: CAMEL-9204
 URL: https://issues.apache.org/jira/browse/CAMEL-9204
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


Currently our documentation says that we should configure topic prefix when 
working with AMQP 1.0.

{code}

   
 
   
 
  
   
   
{code}

We should provide factory method which creates pre-configured component that 
can be used with AMQP 1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9203) camel-amqp should provide qpid dependencies

2015-10-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9203:
-
Issue Type: Improvement  (was: Bug)

> camel-amqp should provide qpid dependencies
> ---
>
> Key: CAMEL-9203
> URL: https://issues.apache.org/jira/browse/CAMEL-9203
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Currently Qpid dependencies are marked as optional:
> {code}
> 
>   org.apache.qpid
>   qpid-amqp-1-0-client-jms
>   ${qpid-version}
>   true
> 
> 
> org.apache.qpid
> qpid-client
> ${qpid-version}
> true
> 
> {code}
> Those should not be optional, as the component is unusable without those two 
> jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-9203) camel-amqp should provide qpid dependnecies

2015-10-09 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-9203:


 Summary: camel-amqp should provide qpid dependnecies
 Key: CAMEL-9203
 URL: https://issues.apache.org/jira/browse/CAMEL-9203
 Project: Camel
  Issue Type: Bug
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.17.0


Currently Qpid dependencies are marked as optional:

{code}

  org.apache.qpid
  qpid-amqp-1-0-client-jms
  ${qpid-version}
  true


org.apache.qpid
qpid-client
${qpid-version}
true

{code}

Those should not be optional, as the component is unusable without those two 
jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9203) camel-amqp should provide qpid dependencies

2015-10-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9203:
-
Summary: camel-amqp should provide qpid dependencies  (was: camel-amqp 
should provide qpid dependnecies)

> camel-amqp should provide qpid dependencies
> ---
>
> Key: CAMEL-9203
> URL: https://issues.apache.org/jira/browse/CAMEL-9203
> Project: Camel
>  Issue Type: Bug
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Currently Qpid dependencies are marked as optional:
> {code}
> 
>   org.apache.qpid
>   qpid-amqp-1-0-client-jms
>   ${qpid-version}
>   true
> 
> 
> org.apache.qpid
> qpid-client
> ${qpid-version}
> true
> 
> {code}
> Those should not be optional, as the component is unusable without those two 
> jars.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9204) Provide AMQP component factory method for AMQP 1.0

2015-10-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9204.
--
Resolution: Fixed

Fixed in 8b4b19faffd17f281db1a24ad5d32e497d35e940.

Users can now call the {{AMQPComponent#amqp10Component(String uri)}} method to 
create the pre-configured AMQP 1.0 component.

> Provide AMQP component factory method for AMQP 1.0
> --
>
> Key: CAMEL-9204
> URL: https://issues.apache.org/jira/browse/CAMEL-9204
> Project: Camel
>  Issue Type: Improvement
>Reporter: Henryk Konsek
>Assignee: Henryk Konsek
> Fix For: 2.17.0
>
>
> Currently our documentation says that we should configure topic prefix when 
> working with AMQP 1.0.
> {code}
>  >
>
>   class="org.apache.qpid.amqp_1_0.jms.impl.ConnectionFactoryImpl" 
> factory-method="createFromURL">
> value="amqp://localhost:5672" />
>  
>   
>
>
> {code}
> We should provide factory method which creates pre-configured component that 
> can be used with AMQP 1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9161) Camel spring-boot not finding routes.

2015-09-25 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907858#comment-14907858
 ] 

Henryk Konsek commented on CAMEL-9161:
--

OK. Thanks! Please let us know what is result. Cheers!

> Camel spring-boot not finding routes.
> -
>
> Key: CAMEL-9161
> URL: https://issues.apache.org/jira/browse/CAMEL-9161
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.15.3
>Reporter: Nicholas Stuart
>Assignee: Henryk Konsek
>
> On startup Camel is not registering any routes annotated with @Component. 
> Route is found and registered in Spring just fine. Switch to version 2.15.2 
> and it works fine. 
> No errors are thrown, and everything says it's started, but no routes are 
> active or reported as being found during startup. 
> Application is being run through `mvn spring-boot:run` if that makes a 
> difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-9161) Camel spring-boot not finding routes.

2015-09-24 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek reassigned CAMEL-9161:


Assignee: Henryk Konsek

> Camel spring-boot not finding routes.
> -
>
> Key: CAMEL-9161
> URL: https://issues.apache.org/jira/browse/CAMEL-9161
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.15.3
>Reporter: Nicholas Stuart
>Assignee: Henryk Konsek
>
> On startup Camel is not registering any routes annotated with @Component. 
> Route is found and registered in Spring just fine. Switch to version 2.15.2 
> and it works fine. 
> No errors are thrown, and everything says it's started, but no routes are 
> active or reported as being found during startup. 
> Application is being run through `mvn spring-boot:run` if that makes a 
> difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9161) Camel spring-boot not finding routes.

2015-09-24 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906746#comment-14906746
 ] 

Henryk Konsek commented on CAMEL-9161:
--

So it works for 2.15.2 and doesn't for 2.15.3?

> Camel spring-boot not finding routes.
> -
>
> Key: CAMEL-9161
> URL: https://issues.apache.org/jira/browse/CAMEL-9161
> Project: Camel
>  Issue Type: Bug
>  Components: camel-spring-boot
>Affects Versions: 2.15.3
>Reporter: Nicholas Stuart
>Assignee: Henryk Konsek
>
> On startup Camel is not registering any routes annotated with @Component. 
> Route is found and registered in Spring just fine. Switch to version 2.15.2 
> and it works fine. 
> No errors are thrown, and everything says it's started, but no routes are 
> active or reported as being found during startup. 
> Application is being run through `mvn spring-boot:run` if that makes a 
> difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-9145) Upgrade camel-hbase component to hbase 1.1.1 on Hadoop 2.7.1

2015-09-18 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805166#comment-14805166
 ] 

Henryk Konsek commented on CAMEL-9145:
--

Hi Wojtek,

The usual approach for the multiple API versions support in Camel is to create 
the another component that might, but doesn't have to, share some code with the 
old component. For example we have Netty (1) and Netty4 (2) components. For 
former supports Netty 3 and the latter supports Netty 4.

So if HBase 1.1.1 API is not compatible with our 0.98 component, I propose to 
create new "hbase1" component which could try to reuse code from the old 
"hbase" one.  

Cheers!

(1) http://camel.apache.org/netty
(2) http://camel.apache.org/netty4

> Upgrade camel-hbase component to hbase 1.1.1 on Hadoop 2.7.1
> 
>
> Key: CAMEL-9145
> URL: https://issues.apache.org/jira/browse/CAMEL-9145
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hbase
>Affects Versions: 2.16.0
>Reporter: Wojciech Indyk
>
> There is a new HBase version with changed API. HBase 1.1.1 is also a part of 
> Hortonworks Data Platform 2.3 http://hortonworks.com/hdp/whats-new/ 
> There are changes in HBase 1.1.1 API in compare to 0.98 (currently in Camel). 
> The question is how to provide two version of camel-hbase (for HBase 0.98 and 
> HBase 1.1.1)?
> I've just started to prepare a version compatible with HBase 1.1.1 and Hadoop 
> 2.7.1



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-07-31 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14649458#comment-14649458
 ] 

Henryk Konsek commented on CAMEL-8554:
--

Thanks Claus!

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Claus Ibsen
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-9029) JGroups managed routes can be started too early

2015-07-28 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-9029.
--
Resolution: Fixed

Fixed and backported to 2.15.3.

 JGroups managed routes can be started too early
 ---

 Key: CAMEL-9029
 URL: https://issues.apache.org/jira/browse/CAMEL-9029
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0, 2.15.3


 {{JGroupsFilters#dropNonCoordinatorViews}} doesn't filter non-view messages 
 properly which can cause the wrong route to be started. This issue was not so 
 easy to detect, as usually the channels used for cluster management doesn't 
 send any other messages, than view ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-9029) JGroups managed routes can be started too early

2015-07-28 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-9029:
-
Description: {{JGroupsFilters#dropNonCoordinatorViews}} doesn't filter 
non-view messages properly which can cause the wrong route to be started. This 
issue was not so easy to detect, as usually the channels used for cluster 
management doesn't send any other messages, than view ones.  (was: 
{{JGroupsFilters#dropNonCoordinatorViews}} doesn't filter non-view messages 
properly which can cause the wrong route to be started.)

 JGroups managed routes can be started too early
 ---

 Key: CAMEL-9029
 URL: https://issues.apache.org/jira/browse/CAMEL-9029
 Project: Camel
  Issue Type: Bug
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0, 2.15.3


 {{JGroupsFilters#dropNonCoordinatorViews}} doesn't filter non-view messages 
 properly which can cause the wrong route to be started. This issue was not so 
 easy to detect, as usually the channels used for cluster management doesn't 
 send any other messages, than view ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8987) Vert.x endpoints should support mutliple consumers

2015-07-20 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8987:


 Summary: Vert.x endpoints should support mutliple consumers
 Key: CAMEL-8987
 URL: https://issues.apache.org/jira/browse/CAMEL-8987
 Project: Camel
  Issue Type: Improvement
  Components: camel-vertx
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.3, 2.16


Vert.x event bus supports pub/sub communication style, so it should be possible 
to connect more than one consumer to the same endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8987) Vert.x endpoints should support mutliple consumers

2015-07-20 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8987:
-
Description: Vert.x event bus supports pub/sub communication style and 
round robin on the queues, so it should be possible to connect more than one 
consumer to the same endpoint.  (was: Vert.x event bus supports pub/sub 
communication style, so it should be possible to connect more than one consumer 
to the same endpoint.)

 Vert.x endpoints should support mutliple consumers
 --

 Key: CAMEL-8987
 URL: https://issues.apache.org/jira/browse/CAMEL-8987
 Project: Camel
  Issue Type: Improvement
  Components: camel-vertx
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.3, 2.16


 Vert.x event bus supports pub/sub communication style and round robin on the 
 queues, so it should be possible to connect more than one consumer to the 
 same endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8987) Vert.x endpoints should support mutliple consumers

2015-07-20 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8987:
-
Fix Version/s: (was: 2.15.3)

 Vert.x endpoints should support mutliple consumers
 --

 Key: CAMEL-8987
 URL: https://issues.apache.org/jira/browse/CAMEL-8987
 Project: Camel
  Issue Type: Improvement
  Components: camel-vertx
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16


 Vert.x event bus supports pub/sub communication style and round robin on the 
 queues, so it should be possible to connect more than one consumer to the 
 same endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8987) Vert.x endpoints should support mutliple consumers

2015-07-20 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8987.
--
Resolution: Fixed

Resolved in da9f0f773f37a09c61c276e0e4b6ac19ab4ba09b.

 Vert.x endpoints should support mutliple consumers
 --

 Key: CAMEL-8987
 URL: https://issues.apache.org/jira/browse/CAMEL-8987
 Project: Camel
  Issue Type: Improvement
  Components: camel-vertx
Affects Versions: 2.15.2
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16


 Vert.x event bus supports pub/sub communication style and round robin on the 
 queues, so it should be possible to connect more than one consumer to the 
 same endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8906) Application hangs when Spring Boot Actuator shutdown hook is used

2015-06-26 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14602665#comment-14602665
 ] 

Henryk Konsek commented on CAMEL-8906:
--

Hi Miroslav,

Please do create pull request - I will merge it. Maybe one thing - can we try 
to add {{completed()}} method to the {{CamelSpringBootApplicationController}} 
instead of using the reflection? Thanks!

Cheers!

 Application hangs when Spring Boot Actuator shutdown hook is used
 -

 Key: CAMEL-8906
 URL: https://issues.apache.org/jira/browse/CAMEL-8906
 Project: Camel
  Issue Type: Sub-task
  Components: camel-spring-boot
Affects Versions: 2.15.2
Reporter: Miroslav Matejovsky

 After some investigation:
 * {{org.apache.camel.spring.boot.CamelSpringBootApplicationController}} 
 creates {{org.apache.camel.main.MainSupport}} instance
 * {{MainSupport.waitUntilCompleted()}} will hang on {{latch.await()}}
 * To release this lock {{MainSupport.completed()}} has to be called. But this 
 never happens
 * CamelSpringBootApplicationController should implement {{@PreDestroy}} 
 callback and call {{mainSupport.completed()}}
 * Workaround:
 {code}
   @Autowired
   private CamelSpringBootApplicationController 
 camelSpringBootApplicationController;
   @PreDestroy
   public void preDestroy() throws Exception {
 final Field f = 
 camelSpringBootApplicationController.getClass().getDeclaredField(mainSupport);
 f.setAccessible(true);
 MainSupport mainSupport = (MainSupport) 
 f.get(camelSpringBootApplicationController);
 mainSupport.completed();
   }
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8801) CamelContext auto-configuration should be conditional

2015-06-02 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8801.
--
   Resolution: Fixed
Fix Version/s: 2.16.0
 Assignee: Henryk Konsek

Pull request has been merged.

 CamelContext auto-configuration should be conditional
 -

 Key: CAMEL-8801
 URL: https://issues.apache.org/jira/browse/CAMEL-8801
 Project: Camel
  Issue Type: Improvement
  Components: camel-spring-boot
Affects Versions: 2.15.2
Reporter: Chris Pimlott
Assignee: Henryk Konsek
 Fix For: 2.16.0


 The {{@Bean}} declaration of {{CamelContext}} within 
 {{CamelAutoConfiguration}} should be made conditional to allow the user to 
 create it manually if they so desire.  This is useful when converting an 
 application using an existing XML-based camelContext, for example.
 This would also make camel-spring-boot more consistent with [Spring Boot's 
 policy of non-invasive 
 auto-configuration|http://docs.spring.io/spring-boot/docs/current-SNAPSHOT/reference/htmlsingle/#using-boot-replacing-auto-configuration].
 The fix is just to add a conditional annotation on the camelContext method, 
 e.g.:
 {code}
 @Bean
 @ConditionalOnMissingBean(CamelContext.class)
 CamelContext camelContext(ApplicationContext applicationContext,
   CamelConfigurationProperties 
 configurationProperties) {
 {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8808) Create Grape component

2015-05-27 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8808:


 Summary: Create Grape component
 Key: CAMEL-8808
 URL: https://issues.apache.org/jira/browse/CAMEL-8808
 Project: Camel
  Issue Type: New Feature
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Is is a demand for Camel runtime patching capabilities for the non-OSGi 
containers. Such capabilities would be especially useful for the MQTT on-air 
updates in the IoT applications. To be exact users would like to:

- load jar at runtime
- dynamically create new route with component deployed in that jar
- create bean/processor using class deployed in that jar
- persist the deployed jars between restarts

This can be achieved using Groovy class loader and Grape (1).

(1) http://docs.groovy-lang.org/latest/html/documentation/grape.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8808) Create Grape component

2015-05-27 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8808.
--
Resolution: Fixed

 Create Grape component
 --

 Key: CAMEL-8808
 URL: https://issues.apache.org/jira/browse/CAMEL-8808
 Project: Camel
  Issue Type: New Feature
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Is is a demand for Camel runtime patching capabilities for the non-OSGi 
 containers. Such capabilities would be especially useful for the MQTT on-air 
 updates in the IoT applications. To be exact users would like to:
 - load jar at runtime
 - dynamically create new route with component deployed in that jar
 - create bean/processor using class deployed in that jar
 - persist the deployed jars between restarts
 This can be achieved using Groovy class loader and Grape (1).
 (1) http://docs.groovy-lang.org/latest/html/documentation/grape.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8808) Create Grape component

2015-05-27 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14561701#comment-14561701
 ] 

Henryk Konsek commented on CAMEL-8808:
--

Committed in 520295b22b03058c5b4149ad7cd5b99c4af9aef3.

 Create Grape component
 --

 Key: CAMEL-8808
 URL: https://issues.apache.org/jira/browse/CAMEL-8808
 Project: Camel
  Issue Type: New Feature
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Is is a demand for Camel runtime patching capabilities for the non-OSGi 
 containers. Such capabilities would be especially useful for the MQTT on-air 
 updates in the IoT applications. To be exact users would like to:
 - load jar at runtime
 - dynamically create new route with component deployed in that jar
 - create bean/processor using class deployed in that jar
 - persist the deployed jars between restarts
 This can be achieved using Groovy class loader and Grape (1).
 (1) http://docs.groovy-lang.org/latest/html/documentation/grape.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8535) Camel-Restlet 2.15.0 setting up SSL

2015-05-15 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8535.
--
Resolution: Won't Fix

Closing then. Feel free to reopen it if needed.

Laters!

 Camel-Restlet 2.15.0 setting up SSL 
 

 Key: CAMEL-8535
 URL: https://issues.apache.org/jira/browse/CAMEL-8535
 Project: Camel
  Issue Type: Bug
  Components: camel-restlet
Affects Versions: 2.15.0
 Environment: JBOSS EAP 6.1, JDK 1.7.0_76-b13
Reporter: Sandeep Poreddy

 Refer to the issue at :
 http://camel.465427.n5.nabble.com/Camel-Restlet-2-15-0-setting-up-SSL-td5764552.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-05-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8460:
-
Fix Version/s: 2.15.3
   2.16.0

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek
 Fix For: 2.16.0, 2.15.3


 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09 08:41:05.096  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: transcodeWorkflowDLQ 
 started and consuming from:

[jira] [Commented] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-05-12 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540109#comment-14540109
 ] 

Henryk Konsek commented on CAMEL-8460:
--

Resolved in 98902f02d143b6e81c8d7f0b8048b1788ecbcb50. Great thanks for the 
patch!

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek

 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09 08:41:05.096  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: transcodeWorkflowDLQ

[jira] [Updated] (CAMEL-8482) Camel requires restart of Spring applicationcontext to fetch new values for properties managed by Spring Cloud

2015-05-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8482:
-
Description: 
When having a camel route builder making use of a property managed by spring  
cloud config server, the beans in the application managed by Spring get the 
property values refreshed when invoking the Spring cloud config RefreshEndpoint 
but the camel routebuilders does not pick up the new values. Restarting the 
camel context does not help either. Restart of Spring application context is 
required.

Example that works for Spring managed beans:

package se.comhem.service;

import org.springframework.beans.factory.annotation.Value;
import org.springframework.cloud.context.config.annotation.RefreshScope;
import org.springframework.stereotype.Component;

@Component
@RefreshScope()
public class CosmosProperties {

@Value(${cosmos.someappconf})
private String someAppConf;

public String getSomeAppConf(){
return someAppConf;
}


}

When using this bean together with a camel routebuilder it does not work until 
Spring Application context is restarted:

package se.comhem.service;

import org.apache.camel.model.language.SimpleExpression;
import org.apache.camel.spring.SpringRouteBuilder;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Component;

@Component
public class ConfigClientRouteBuilder extends SpringRouteBuilder {
pansowa
private final static String URI = servlet:///testCamel;

@Autowired
private CosmosProperties cosmosProperties;

@Override
public void configure() throws Exception {
from(URI)
.setBody(new 
SimpleExpression(cosmosProperties.getSomeAppConf()))
.to(log:se.comhem?level=INFOshowBody=truemultiline=true)
.end();

}

}

Main application class:

package se.comhem.service;

import org.apache.camel.component.servlet.CamelHttpTransportServlet;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
import org.springframework.boot.context.embedded.ServletRegistrationBean;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.ComponentScan;
import org.springframework.context.annotation.Configuration;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RestController;

@Configuration
@EnableAutoConfiguration
@RestController
@ComponentScan
public class Application {

private static final String CAMEL_URL_MAPPING = /camel/*;
private static final String CAMEL_SERVLET_NAME = CamelServlet;

@Autowired
private CosmosProperties cosmosProperties;

@RequestMapping(/)
public String home() {
return Config client running correctly;
}

public static void main( String[] args ) {
SpringApplication.run(Application.class, args);
}

@RequestMapping(/some-app-conf)
public String someAppConf(){
return Some app conf  + this.cosmosProperties.getSomeAppConf();
}

@Bean
public ServletRegistrationBean servletRegistrationBean() {
ServletRegistrationBean registration = new ServletRegistrationBean(new 
CamelHttpTransportServlet(), CAMEL_URL_MAPPING);
registration.setName(CAMEL_SERVLET_NAME);
return registration;
}

}

Bootstrap configuration

spring:
  boot:
admin:
  url: http://localhost:8880
  application:
name: config-client
  config:
name: config-client
  profiles:
  active: ${environment}
  cloud:
  config:
uri: http://localhost:8110
enabled: true
failFast: true

pom:

?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion

groupIdse.comhem.service/groupId
artifactIdconfig-client/artifactId
version1.0-SNAPSHOT/version

properties
org.springframework.version4.1.5.RELEASE/org.springframework.version
camel.version2.15.0/camel.version
java.version1.8/java.version
/properties

dependencyManagement
dependencies
dependency
groupIdorg.springframework.cloud/groupId
artifactIdspring-cloud-starter-parent/artifactId
version1.0.0.RELEASE/version
typepom/type
scopeimport/scope
/dependency
/dependencies
/dependencyManagement

dependencies

dependency
groupIdorg.springframework.boot/groupId
artifactIdspring-boot-starter-web/artifactId
exclusions

[jira] [Resolved] (CAMEL-8482) Camel requires restart of Spring applicationcontext to fetch new values for properties managed by Spring Cloud

2015-05-12 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8482.
--
Resolution: Cannot Reproduce

Let me know if you can help me to reproduce this issue. In the meantime, I'm 
closing the ticket.

 Camel requires restart of Spring applicationcontext to fetch new values for 
 properties managed by Spring Cloud
 --

 Key: CAMEL-8482
 URL: https://issues.apache.org/jira/browse/CAMEL-8482
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Manuel Rivas
Assignee: Henryk Konsek
 Attachments: config-client.zip


 When having a camel route builder making use of a property managed by spring  
 cloud config server, the beans in the application managed by Spring get the 
 property values refreshed when invoking the Spring cloud config 
 RefreshEndpoint but the camel routebuilders does not pick up the new values. 
 Restarting the camel context does not help either. Restart of Spring 
 application context is required.
 Example that works for Spring managed beans:
 package se.comhem.service;
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.cloud.context.config.annotation.RefreshScope;
 import org.springframework.stereotype.Component;
 @Component
 @RefreshScope()
 public class CosmosProperties {
 @Value(${cosmos.someappconf})
 private String someAppConf;
 public String getSomeAppConf(){
 return someAppConf;
 }
 }
 When using this bean together with a camel routebuilder it does not work 
 until Spring Application context is restarted:
 package se.comhem.service;
 import org.apache.camel.model.language.SimpleExpression;
 import org.apache.camel.spring.SpringRouteBuilder;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.stereotype.Component;
 @Component
 public class ConfigClientRouteBuilder extends SpringRouteBuilder {
 pansowa
 private final static String URI = servlet:///testCamel;
 @Autowired
 private CosmosProperties cosmosProperties;
 @Override
 public void configure() throws Exception {
 from(URI)
 .setBody(new 
 SimpleExpression(cosmosProperties.getSomeAppConf()))
 .to(log:se.comhem?level=INFOshowBody=truemultiline=true)
 .end();
 }
 }
 Main application class:
 package se.comhem.service;
 import org.apache.camel.component.servlet.CamelHttpTransportServlet;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.boot.SpringApplication;
 import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
 import org.springframework.boot.context.embedded.ServletRegistrationBean;
 import org.springframework.context.annotation.Bean;
 import org.springframework.context.annotation.ComponentScan;
 import org.springframework.context.annotation.Configuration;
 import org.springframework.web.bind.annotation.RequestMapping;
 import org.springframework.web.bind.annotation.RestController;
 @Configuration
 @EnableAutoConfiguration
 @RestController
 @ComponentScan
 public class Application {
 private static final String CAMEL_URL_MAPPING = /camel/*;
 private static final String CAMEL_SERVLET_NAME = CamelServlet;
 @Autowired
 private CosmosProperties cosmosProperties;
 @RequestMapping(/)
 public String home() {
 return Config client running correctly;
 }
 public static void main( String[] args ) {
 SpringApplication.run(Application.class, args);
 }
 @RequestMapping(/some-app-conf)
 public String someAppConf(){
 return Some app conf  + this.cosmosProperties.getSomeAppConf();
 }
 @Bean
 public ServletRegistrationBean servletRegistrationBean() {
 ServletRegistrationBean registration = new 
 ServletRegistrationBean(new CamelHttpTransportServlet(), CAMEL_URL_MAPPING);
 registration.setName(CAMEL_SERVLET_NAME);
 return registration;
 }
 }
 Bootstrap configuration
 spring:
   boot:
 admin:
   url: http://localhost:8880
   application:
 name: config-client
   config:
 name: config-client
   profiles:
   active: ${environment}
   cloud:
   config:
 uri: http://localhost:8110
 enabled: true
 failFast: true
 pom:
 ?xml version=1.0 encoding=UTF-8?
 project xmlns=http://maven.apache.org/POM/4.0.0;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/xsd/maven-4.0.0.xsd;
 modelVersion4.0.0/modelVersion
 groupIdse.comhem.service/groupId
 artifactIdconfig-client/artifactId

[jira] [Reopened] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-05-06 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek reopened CAMEL-8460:
--

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09 08:41:05.096  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: transcodeWorkflowDLQ 
 started and consuming from: Endpoint[direct://transcodeWorkflowDLQ]
 2015-03-09 08:41:05.098  INFO

[jira] [Updated] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-05-06 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8460:
-
Fix Version/s: (was: 2.15.2)
   (was: 2.16.0)

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek

 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09 08:41:05.096  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: transcodeWorkflowDLQ 
 started and consuming from:

[jira] [Commented] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-05-06 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14531266#comment-14531266
 ] 

Henryk Konsek commented on CAMEL-8460:
--

Yeah, parent application context might be the corner case here. Let me verify 
this with the unit test and merge your fix. Thanks for catching this!

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek

 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09 08:41:05.096  INFO 81935 --- [   main]

[jira] [Resolved] (CAMEL-8743) Broken link in OGNL component documentation

2015-05-05 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8743.
--
Resolution: Fixed

Fixed. Thanks for reporting!

BTW Maybe you would like to have write access to our wiki?

 Broken link in OGNL component documentation
 ---

 Key: CAMEL-8743
 URL: https://issues.apache.org/jira/browse/CAMEL-8743
 Project: Camel
  Issue Type: Bug
  Components: documentation
Reporter: David Keen

 The first link on the OGNL component documentation page is broken.
 Text is Camel allows OGNL to be used...
 Correct link should be http://commons.apache.org/proper/commons-ognl/.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8736) Create new component using Hazelcast JCache implementation

2015-05-04 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14526730#comment-14526730
 ] 

Henryk Konsek commented on CAMEL-8736:
--

Hi,

Here is the thread (1) regarding the general cache component for Camel. I 
wanted to contribute it, but I got more important stuff on my plate in the 
meantime.

Cheers.

(1) 
http://camel.465427.n5.nabble.com/Re-An-idea-of-new-camel-cache-endpoint-td5753365.html

 Create new component using Hazelcast JCache implementation
 --

 Key: CAMEL-8736
 URL: https://issues.apache.org/jira/browse/CAMEL-8736
 Project: Camel
  Issue Type: Improvement
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
Priority: Minor
  Labels: caching
 Fix For: Future


 Starting from version 3.3.1, Hazelcast has its own implementation of JCache. 
 I think it can be useful to include it in Camel as a component.
 Edit:
 Looking at the implementation it looks like this new feature is outside the 
 HazelcastInstance. So this improvement can be part of a new component, like 
 camel-hazelcast-cache, but it can't be inside camel-hazelcast component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8722) File consumer - Allow to plugin a custom ExceptionHandler for the on completion unit of work

2015-04-30 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521566#comment-14521566
 ] 

Henryk Konsek commented on CAMEL-8722:
--

Thanks Claus. That was fast :) .

 File consumer - Allow to plugin a custom ExceptionHandler for the on 
 completion unit of work
 

 Key: CAMEL-8722
 URL: https://issues.apache.org/jira/browse/CAMEL-8722
 Project: Camel
  Issue Type: Improvement
  Components: camel-core
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.16.0


 This allows end users to do custom code if an exception was thrown from the 
 file consumer, when it attempts to delete / move files when the consumer was 
 done routing the file.
 By default the consumer would catch the exception and do a WARN log. This 
 ticket allows to plugin a custom code to handle the exception.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8723) Add desired message type to ProducerTemplate.sendBody methods

2015-04-30 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14521565#comment-14521565
 ] 

Henryk Konsek commented on CAMEL-8723:
--

I really like the idea. That would make using {{typeConverter}} for the 
template users much easier. And +1 for the {{sendBodyAs}} method name.

 Add desired message type to ProducerTemplate.sendBody methods
 -

 Key: CAMEL-8723
 URL: https://issues.apache.org/jira/browse/CAMEL-8723
 Project: Camel
  Issue Type: New Feature
  Components: camel-core
Affects Versions: 2.15.1
Reporter: Geert Schuring
  Labels: pojo, type-converter
 Fix For: 2.16.0


 Using Pojo Messaging annotations, Camel automatically uses the Type Converter 
 system to unmarshall XML messages to JAXB objects in the following scenario:
 {code:java}
 public class CamelPojoDemo {
   
 @Produce(uri = amq:camelpojodemo.reply)
 private ProducerTemplate producer;
   
 @Consume(uri = amq:camelpojodemo.request)
 public void trigger(UpdateMarketDataMessage message) {
   String result = Processed prices:  + 
 message.getMarketData().getPrices().size();
   producer.sendBody(result);
 }
 }
 {code}
 However, handing the producer a JAXB object and expecting it to marshall it 
 to XML before sending it does not seem possible in the current API.
 I would like to propose to add the following method to the ProducerTemplate:
 {code}
   /**
  * Sends the body to the default endpoint after converting it to the 
 given type
  * br/br/
  * p/bNotice:/b that if the processing of the exchange failed with 
 an Exception
  * it is thrown from this method as a {@link 
 org.apache.camel.CamelExecutionException} with
  * the caused exception wrapped.
  *
  * @param body the payload to send
  * @param type the type which the body should be converted to before 
 sending
  * @throws CamelExecutionException if the processing of the exchange 
 failed
  */
 void sendBody(Object body, Class type) throws CamelExecutionException;
 {code}
 This would allow users to send a JAXB object and instruct Camel to use its 
 Type Converter system to marshall the object to XML:
 {code}
 producer.sendBody(jaxbObject, String.class);
 {code}
 Note: The sendBody, sendBodyAndHeader and sendBodyAndProperty methods are all 
 overloaded several times which could mean quite a number of new methods. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8482) Camel requires restart of Spring applicationcontext to fetch new values for properties managed by Spring Cloud

2015-04-27 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513901#comment-14513901
 ] 

Henryk Konsek commented on CAMEL-8482:
--

Hi Manuel,

Actually it looks more like a Spring Boot issue, than Camel issue. Can you send 
me the Maven example I could use to reproduce the issue?

Cheers.

 Camel requires restart of Spring applicationcontext to fetch new values for 
 properties managed by Spring Cloud
 --

 Key: CAMEL-8482
 URL: https://issues.apache.org/jira/browse/CAMEL-8482
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Manuel Rivas
Assignee: Henryk Konsek
 Attachments: config-client.zip


 When having a camel route builder making use of a property managed by spring  
 cloud config server, the beans in the application managed by Spring get the 
 property values refreshed when invoking the Spring cloud config 
 RefreshEndpoint but the camel routebuilders does not pick up the new values. 
 Restarting the camel context does not help either. Restart of Spring 
 application context is required.
 Example that works for Spring managed beans:
 package se.comhem.service;
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.cloud.context.config.annotation.RefreshScope;
 import org.springframework.stereotype.Component;
 @Component
 @RefreshScope()
 public class CosmosProperties {
 @Value(${cosmos.someappconf})
 private String someAppConf;
 public String getSomeAppConf(){
 return someAppConf;
 }
 }
 When using this bean together with a camel routebuilder it does not work 
 until Spring Application context is restarted:
 package se.comhem.service;
 import org.apache.camel.model.language.SimpleExpression;
 import org.apache.camel.spring.SpringRouteBuilder;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.stereotype.Component;
 @Component
 public class ConfigClientRouteBuilder extends SpringRouteBuilder {
 private final static String URI = servlet:///testCamel;
 @Autowired
 private CosmosProperties cosmosProperties;
 @Override
 public void configure() throws Exception {
 from(URI)
 .setBody(new 
 SimpleExpression(cosmosProperties.getSomeAppConf()))
 .to(log:se.comhem?level=INFOshowBody=truemultiline=true)
 .end();
 }
 }
 Main application class:
 package se.comhem.service;
 import org.apache.camel.component.servlet.CamelHttpTransportServlet;
 import org.springframework.beans.factory.annotation.Autowired;
 import org.springframework.boot.SpringApplication;
 import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
 import org.springframework.boot.context.embedded.ServletRegistrationBean;
 import org.springframework.context.annotation.Bean;
 import org.springframework.context.annotation.ComponentScan;
 import org.springframework.context.annotation.Configuration;
 import org.springframework.web.bind.annotation.RequestMapping;
 import org.springframework.web.bind.annotation.RestController;
 @Configuration
 @EnableAutoConfiguration
 @RestController
 @ComponentScan
 public class Application {
 private static final String CAMEL_URL_MAPPING = /camel/*;
 private static final String CAMEL_SERVLET_NAME = CamelServlet;
 @Autowired
 private CosmosProperties cosmosProperties;
 @RequestMapping(/)
 public String home() {
 return Config client running correctly;
 }
 public static void main( String[] args ) {
 SpringApplication.run(Application.class, args);
 }
 @RequestMapping(/some-app-conf)
 public String someAppConf(){
 return Some app conf  + this.cosmosProperties.getSomeAppConf();
 }
 @Bean
 public ServletRegistrationBean servletRegistrationBean() {
 ServletRegistrationBean registration = new 
 ServletRegistrationBean(new CamelHttpTransportServlet(), CAMEL_URL_MAPPING);
 registration.setName(CAMEL_SERVLET_NAME);
 return registration;
 }
 }
 Bootstrap configuration
 spring:
   boot:
 admin:
   url: http://localhost:8880
   application:
 name: config-client
   config:
 name: config-client
   profiles:
   active: ${environment}
   cloud:
   config:
 uri: http://localhost:8110
 enabled: true
 failFast: true
 pom:
 ?xml version=1.0 encoding=UTF-8?
 project xmlns=http://maven.apache.org/POM/4.0.0;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/xsd/maven-4.0.0.xsd;
 modelVersion4.0.0/modelVersion

[jira] [Commented] (CAMEL-8701) Camel-Docker tests fails

2015-04-26 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513185#comment-14513185
 ] 

Henryk Konsek commented on CAMEL-8701:
--

Can you share your Docker server version?

Cheers.

 Camel-Docker tests fails
 

 Key: CAMEL-8701
 URL: https://issues.apache.org/jira/browse/CAMEL-8701
 Project: Camel
  Issue Type: Test
  Components: camel-docker
Reporter: Andrea Cosentino
Priority: Minor
 Fix For: 2.16.0


 The camel-docker tests don't work anymore. It seems that the connection to 
 localhost:5000 used in the base header test is refused every time and then we 
 get an out of memory PermGen space.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8655) Create Spring Boot examples and archetypes

2015-04-24 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14510598#comment-14510598
 ] 

Henryk Konsek commented on CAMEL-8655:
--

I have created the basic Spring Boot example - 
https://github.com/apache/camel/tree/master/examples/camel-example-spring-boot 
. I will create more specialized examples soon (plus archetypes).

 Create Spring Boot examples and archetypes
 --

 Key: CAMEL-8655
 URL: https://issues.apache.org/jira/browse/CAMEL-8655
 Project: Camel
  Issue Type: Task
  Components: camel-spring-boot
Reporter: Henryk Konsek
Assignee: Henryk Konsek

 It would be nice with a camel-spring-boot example in 
 https://github.com/apache/camel/tree/master/examples and an archetype 
 https://github.com/apache/camel/tree/master/tooling/archetypes. I would love 
 being able to demo using vanilla camel examples / archetypes and then run em 
 with fabric8 / docker easily. And then having those examples will help on the 
 camel microservice story.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8685) Netty should resolve OPTIONS prefix matches earlier

2015-04-22 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8685:


 Summary: Netty should resolve OPTIONS prefix matches earlier
 Key: CAMEL-8685
 URL: https://issues.apache.org/jira/browse/CAMEL-8685
 Project: Camel
  Issue Type: Improvement
  Components: camel-netty-http, camel-netty4-http
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


Currently it is impossible to define wildcard URI that will serve custom 
OPTIONS response to all the requests:

{code}
   
from(netty4-http:http://0.0.0.0:{{port}}/path1?httpMethodRestrict=POST;).setBody().constant(somePostResponse);

from(netty4-http:http://0.0.0.0:{{port}}?matchOnUriPrefix=truehttpMethodRestrict=OPTIONS;).setBody().constant(expectedOptionsResponse);
{code}

POST route is detected as match for OPTION method too early and the second 
route is never called.

Netty HTTP should be smart enough to find out that there is the wildcard route 
serving OPTION requests and prefer that route over the default OPTION response 
generated by the POST routes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8685) Netty should resolve OPTIONS prefix matches earlier

2015-04-22 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8685.
--
Resolution: Fixed

Resolved in 5b27ecc8aae83f6a4a8b1cd14133387f01d77151.

 Netty should resolve OPTIONS prefix matches earlier
 ---

 Key: CAMEL-8685
 URL: https://issues.apache.org/jira/browse/CAMEL-8685
 Project: Camel
  Issue Type: Improvement
  Components: camel-netty-http, camel-netty4-http
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 Currently it is impossible to define wildcard URI that will serve custom 
 OPTIONS response to all the requests:
 {code}

 from(netty4-http:http://0.0.0.0:{{port}}/path1?httpMethodRestrict=POST;).setBody().constant(somePostResponse);
 
 from(netty4-http:http://0.0.0.0:{{port}}?matchOnUriPrefix=truehttpMethodRestrict=OPTIONS;).setBody().constant(expectedOptionsResponse);
 {code}
 POST route is detected as match for OPTION method too early and the second 
 route is never called.
 Netty HTTP should be smart enough to find out that there is the wildcard 
 route serving OPTION requests and prefer that route over the default OPTION 
 response generated by the POST routes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8685) Netty should resolve OPTIONS prefix matches earlier

2015-04-22 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506924#comment-14506924
 ] 

Henryk Konsek commented on CAMEL-8685:
--

Backported to 2.15.2 in 517db207815e36c32cdd510bed84b85df3b8b54a.

 Netty should resolve OPTIONS prefix matches earlier
 ---

 Key: CAMEL-8685
 URL: https://issues.apache.org/jira/browse/CAMEL-8685
 Project: Camel
  Issue Type: Improvement
  Components: camel-netty-http, camel-netty4-http
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 Currently it is impossible to define wildcard URI that will serve custom 
 OPTIONS response to all the requests:
 {code}

 from(netty4-http:http://0.0.0.0:{{port}}/path1?httpMethodRestrict=POST;).setBody().constant(somePostResponse);
 
 from(netty4-http:http://0.0.0.0:{{port}}?matchOnUriPrefix=truehttpMethodRestrict=OPTIONS;).setBody().constant(expectedOptionsResponse);
 {code}
 POST route is detected as match for OPTION method too early and the second 
 route is never called.
 Netty HTTP should be smart enough to find out that there is the wildcard 
 route serving OPTION requests and prefer that route over the default OPTION 
 response generated by the POST routes. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-04-21 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8460.
--
Resolution: Fixed

Let me close this one. It is a corner case, which is hard to reproduce even in 
Camel 2.15, while it is definitely fixed in Camel 2.16. Feel free to reopen the 
case if you don't agree with me :) .

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from: Endpoint[direct://updateRoomRepo]
 2015-03-09

[jira] [Commented] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-04-21 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505749#comment-14505749
 ] 

Henryk Konsek commented on CAMEL-8460:
--

Also if you create your processor as a Spring bean, you are guaranteed that it 
follows the Spring lifecycle. I.e. it is a singleton created/destroyed together 
with the Spring context.

 camel-spring-boot - Routes restart during startup
 -

 Key: CAMEL-8460
 URL: https://issues.apache.org/jira/browse/CAMEL-8460
 Project: Camel
  Issue Type: Bug
  Components: camel-spring-boot
Affects Versions: 2.15.0
Reporter: Steven Marcus
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 The latest snapshot fixes the issue with my routes not being found.
 But there is still some undesirable behaviour with routes being restarted 
 during the context refresh.
 Here's the console log that shows shutdown handlers being run during app 
 startup... tia
 .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
 ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.2.RELEASE)
 2015-03-09 08:40:55.162  INFO 81935 --- [   main] 
 mediaroom.MRServicesApp  : Starting MRServicesApp on 
 MBP13.local with PID 81935 
 (/Users/srnm/Documents/workspace-buffdubs/MRServices/target/classes started 
 by srnm in /Users/srnm/Documents/workspace-buffdubs/MRServices)
 2015-03-09 08:40:55.165 DEBUG 81935 --- [   main] 
 mediaroom.MRServicesApp  : Running with Spring Boot 
 v1.2.2.RELEASE, Spring v4.1.5.RELEASE
 ...
 [AppClassLoader@14dad5dc] info AspectJ Weaver Version 1.8.5 built on Thursday 
 Jan 29, 2015 at 01:03:58 GMT
 [AppClassLoader@14dad5dc] info register classloader 
 sun.misc.Launcher$AppClassLoader@14dad5dc
 [AppClassLoader@14dad5dc] info using configuration 
 /Users/srnm/Documents/workspace-buffdubs/MRServices/src/main/resources/META-INF/aop.xml
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.AsynchronousAspect
 [AppClassLoader@14dad5dc] info register aspect 
 com.amazonaws.services.simpleworkflow.flow.aspectj.ExponentialRetryAspect
 [AppClassLoader@14dad5dc] warning javax.* types are not being woven because 
 the weaver option '-Xset:weaveJavaxPackages=true' has not been specified
 2015-03-09 08:41:03.406  INFO 81935 --- [   main] 
 o.a.c.i.converter.DefaultTypeConverter   : Loaded 183 type converters
 2015-03-09 08:41:04.345 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Post-processing CamelContext bean: 
 camel-1
 2015-03-09 08:41:04.346 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.394  INFO 81935 --- [   main] 
 o.a.camel.component.log.LogComponent : Using custom Logger: 
 Logger[camelLogger]
 2015-03-09 08:41:04.630 DEBUG 81935 --- [   main] 
 o.a.camel.spring.boot.RoutesCollector: Injecting following route into the 
 CamelContext: Routes: []
 2015-03-09 08:41:04.632  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Apache Camel 2.15-SNAPSHOT 
 (CamelContext: camel-1) is starting
 2015-03-09 08:41:04.633  INFO 81935 --- [   main] 
 o.a.c.m.ManagedManagementStrategy: JMX is enabled
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : AllowUseOriginalMessage is 
 enabled. If access to the original message is not needed, then its 
 recommended to turn this option off as it may improve performance.
 2015-03-09 08:41:04.932  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : StreamCaching is not in use. If 
 using streams then its recommended to enable stream caching. See more details 
 at http://camel.apache.org/stream-caching.html
 2015-03-09 08:41:05.089  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: roomSyncDLQ started and 
 consuming from: Endpoint[direct://roomSyncDLQ]
 2015-03-09 08:41:05.090  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: syncAllRooms started and 
 consuming from: Endpoint[timer://roomSyncTimer?delay=3speriod=30s]
 2015-03-09 08:41:05.092  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: writeRoomSync started and 
 consuming from: Endpoint[direct://writeRoomSync]
 2015-03-09 08:41:05.095  INFO 81935 --- [   main] 
 o.a.camel.spring.SpringCamelContext  : Route: updateRoomRepo started and 
 consuming from:

[jira] [Assigned] (CAMEL-8667) java.lang.NullPointerException CamelSpringTestContextLoader.java:174

2015-04-21 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek reassigned CAMEL-8667:


Assignee: Henryk Konsek

 java.lang.NullPointerException CamelSpringTestContextLoader.java:174
 

 Key: CAMEL-8667
 URL: https://issues.apache.org/jira/browse/CAMEL-8667
 Project: Camel
  Issue Type: Bug
  Components: camel-spring
Affects Versions: 2.15.1
Reporter: Chris Love
Assignee: Henryk Konsek
 Fix For: 2.14.3, 2.15.2, 2.16.0

 Attachments: DailyWeatherDataBeanUnmarshallTest.java


 I am getting a NPE with camel spring unit testing.  I am trying to convert 
 https://github.com/apache/camel/blob/master/components/camel-bindy/src/test/java/org/apache/camel/dataformat/bindy/fixed/unmarshall/simple/trim/BindySimpleFixedLengthUnmarshallTest.java
  
 to pure annotations ... and I am getting a NPE ... 
 I am using:
 {code:java}
 @ContextConfiguration()
 @RunWith(SpringJUnit4ClassRunner.class)
 @BoostrapWith(CamelTestContextBootstrapper.class)
 {code}
 Here is my stack trace.
 {code:java}
 Caused by: java.lang.NullPointerException: null 
 at 
 org.apache.camel.test.spring.CamelSpringTestContextLoader.cleanup(CamelSpringTestContextLoader.java:174)
 at 
 org.apache.camel.test.spring.CamelSpringTestContextLoader.loadContext(CamelSpringTestContextLoader.java:86)
  
 at 
 org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:68)
 at 
 org.springframework.test.context.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:86)
 at 
 org.springframework.test.context.DefaultTestContext.getApplicationContext(DefaultTestContext.java:72)
 {code}
 The unit test is attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-04-18 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501564#comment-14501564
 ] 

Henryk Konsek edited comment on CAMEL-8460 at 4/18/15 7:54 PM:
---

Hi Steven,

I've just tried to execute the following test against the Camel master 
(2.16-SNAPSHOT):

{code}
@SpringBootApplication
public class DoubleStartTest extends FatJarRouter {

@Override
public void configure() throws Exception {
from(direct:test).to(mock:test);
}

@Test
public void xxx() {
DoubleStartTest.main(--spring.main.sources= + 
DoubleStartTest.class.getName());
}

}
{code}

Everything seems to work like a charm. The routes and context have been started 
only once:

{code}
Running org.apache.camel.spring.boot.testme.DoubleStartTest
  .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.3.RELEASE)

2015-04-18 21:46:40.823  INFO 28438 --- [   main] 
o.apache.camel.spring.boot.FatJarRouter  : Starting FatJarRouter on henryberg 
with PID 28438 
(/home/hekonsek/projects/camel/components/camel-spring-boot/target/classes 
started by hekonsek in 
/home/hekonsek/projects/camel/components/camel-spring-boot)
2015-04-18 21:46:40.856  INFO 28438 --- [   main] 
ationConfigEmbeddedWebApplicationContext : Refreshing 
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@402e37bc:
 startup date [Sat Apr 18 21:46:40 CEST 2015]; root of context hierarchy
2015-04-18 21:46:41.273  INFO 28438 --- [   main] 
o.s.b.f.s.DefaultListableBeanFactory : Overriding bean definition for bean 
'beanNameViewResolver': replacing [Root bean: class [null]; scope=; 
abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; 
autowireCandidate=true; primary=false; 
factoryBeanName=org.springframework.boot.autoconfigure.web.ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration;
 factoryMethodName=beanNameViewResolver; initMethodName=null; 
destroyMethodName=(inferred); defined in class path resource 
[org/springframework/boot/autoconfigure/web/ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration.class]]
 with [Root bean: class [null]; scope=; abstract=false; lazyInit=false; 
autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; 
factoryBeanName=org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter;
 factoryMethodName=beanNameViewResolver; initMethodName=null; 
destroyMethodName=(inferred); defined in class path resource 
[org/springframework/boot/autoconfigure/web/WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter.class]]
2015-04-18 21:46:41.597  INFO 28438 --- [   main] 
trationDelegate$BeanPostProcessorChecker : Bean 
'org.apache.camel.spring.boot.CamelAutoConfiguration' of type [class 
org.apache.camel.spring.boot.CamelAutoConfiguration$$EnhancerBySpringCGLIB$$369735a8]
 is not eligible for getting processed by all BeanPostProcessors (for example: 
not eligible for auto-proxying)
2015-04-18 21:46:41.895  INFO 28438 --- [   main] 
s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 
8080 (http)
2015-04-18 21:46:42.088  INFO 28438 --- [   main] 
o.apache.catalina.core.StandardService   : Starting service Tomcat
2015-04-18 21:46:42.090  INFO 28438 --- [   main] 
org.apache.catalina.core.StandardEngine  : Starting Servlet Engine: Apache 
Tomcat/8.0.20
2015-04-18 21:46:42.217  INFO 28438 --- [ost-startStop-1] 
o.a.c.c.C.[Tomcat].[localhost].[/]   : Initializing Spring embedded 
WebApplicationContext
2015-04-18 21:46:42.217  INFO 28438 --- [ost-startStop-1] 
o.s.web.context.ContextLoader: Root WebApplicationContext: 
initialization completed in 1365 ms
2015-04-18 21:46:42.757  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.e.ServletRegistrationBean: Mapping servlet: 'dispatcherServlet' 
to [/]
2015-04-18 21:46:42.760  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.embedded.FilterRegistrationBean  : Mapping filter: 
'characterEncodingFilter' to: [/*]
2015-04-18 21:46:42.760  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.embedded.FilterRegistrationBean  : Mapping filter: 
'hiddenHttpMethodFilter' to: [/*]
2015-04-18 21:46:43.031  INFO 28438 --- [   main] 
s.w.s.m.m.a.RequestMappingHandlerAdapter : Looking for @ControllerAdvice: 
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@402e37bc:
 startup date [Sat Apr 18 21:46:40 CEST 2015]; root of context hierarchy
2015-04-18 21:46:43.081  INFO 28438 --- [   main] 
s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped

[jira] [Commented] (CAMEL-8460) camel-spring-boot - Routes restart during startup

2015-04-18 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501564#comment-14501564
 ] 

Henryk Konsek commented on CAMEL-8460:
--

Hi Steven,

I've just tried to execute the following test against the Camel master 
(2.16.-SNAPSHOT):

{code}
@SpringBootApplication
public class DoubleStartTest extends FatJarRouter {

@Override
public void configure() throws Exception {
from(direct:test).to(mock:test);
}

@Test
public void xxx() {
DoubleStartTest.main(--spring.main.sources= + 
DoubleStartTest.class.getName());
}

}
{code}

Everything seems to work like a charm. The routes and context have been started 
only once:

{code}
Running org.apache.camel.spring.boot.testme.DoubleStartTest
  .     ___ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  || .__|_| |_|_| |_\__, | / / / /
 =|_|==|___/=/_/_/_/
 :: Spring Boot ::(v1.2.3.RELEASE)

2015-04-18 21:46:40.823  INFO 28438 --- [   main] 
o.apache.camel.spring.boot.FatJarRouter  : Starting FatJarRouter on henryberg 
with PID 28438 
(/home/hekonsek/projects/camel/components/camel-spring-boot/target/classes 
started by hekonsek in 
/home/hekonsek/projects/camel/components/camel-spring-boot)
2015-04-18 21:46:40.856  INFO 28438 --- [   main] 
ationConfigEmbeddedWebApplicationContext : Refreshing 
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@402e37bc:
 startup date [Sat Apr 18 21:46:40 CEST 2015]; root of context hierarchy
2015-04-18 21:46:41.273  INFO 28438 --- [   main] 
o.s.b.f.s.DefaultListableBeanFactory : Overriding bean definition for bean 
'beanNameViewResolver': replacing [Root bean: class [null]; scope=; 
abstract=false; lazyInit=false; autowireMode=3; dependencyCheck=0; 
autowireCandidate=true; primary=false; 
factoryBeanName=org.springframework.boot.autoconfigure.web.ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration;
 factoryMethodName=beanNameViewResolver; initMethodName=null; 
destroyMethodName=(inferred); defined in class path resource 
[org/springframework/boot/autoconfigure/web/ErrorMvcAutoConfiguration$WhitelabelErrorViewConfiguration.class]]
 with [Root bean: class [null]; scope=; abstract=false; lazyInit=false; 
autowireMode=3; dependencyCheck=0; autowireCandidate=true; primary=false; 
factoryBeanName=org.springframework.boot.autoconfigure.web.WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter;
 factoryMethodName=beanNameViewResolver; initMethodName=null; 
destroyMethodName=(inferred); defined in class path resource 
[org/springframework/boot/autoconfigure/web/WebMvcAutoConfiguration$WebMvcAutoConfigurationAdapter.class]]
2015-04-18 21:46:41.597  INFO 28438 --- [   main] 
trationDelegate$BeanPostProcessorChecker : Bean 
'org.apache.camel.spring.boot.CamelAutoConfiguration' of type [class 
org.apache.camel.spring.boot.CamelAutoConfiguration$$EnhancerBySpringCGLIB$$369735a8]
 is not eligible for getting processed by all BeanPostProcessors (for example: 
not eligible for auto-proxying)
2015-04-18 21:46:41.895  INFO 28438 --- [   main] 
s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 
8080 (http)
2015-04-18 21:46:42.088  INFO 28438 --- [   main] 
o.apache.catalina.core.StandardService   : Starting service Tomcat
2015-04-18 21:46:42.090  INFO 28438 --- [   main] 
org.apache.catalina.core.StandardEngine  : Starting Servlet Engine: Apache 
Tomcat/8.0.20
2015-04-18 21:46:42.217  INFO 28438 --- [ost-startStop-1] 
o.a.c.c.C.[Tomcat].[localhost].[/]   : Initializing Spring embedded 
WebApplicationContext
2015-04-18 21:46:42.217  INFO 28438 --- [ost-startStop-1] 
o.s.web.context.ContextLoader: Root WebApplicationContext: 
initialization completed in 1365 ms
2015-04-18 21:46:42.757  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.e.ServletRegistrationBean: Mapping servlet: 'dispatcherServlet' 
to [/]
2015-04-18 21:46:42.760  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.embedded.FilterRegistrationBean  : Mapping filter: 
'characterEncodingFilter' to: [/*]
2015-04-18 21:46:42.760  INFO 28438 --- [ost-startStop-1] 
o.s.b.c.embedded.FilterRegistrationBean  : Mapping filter: 
'hiddenHttpMethodFilter' to: [/*]
2015-04-18 21:46:43.031  INFO 28438 --- [   main] 
s.w.s.m.m.a.RequestMappingHandlerAdapter : Looking for @ControllerAdvice: 
org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@402e37bc:
 startup date [Sat Apr 18 21:46:40 CEST 2015]; root of context hierarchy
2015-04-18 21:46:43.081  INFO 28438 --- [   main] 
s.w.s.m.m.a.RequestMappingHandlerMapping : Mapped 
{[/error],methods=[],params=[],headers=[],consumes=[],produces=[text/html],custom=[]}
 onto public

[jira] [Created] (CAMEL-8655) Create Spring Boot examples and archetypes

2015-04-17 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8655:


 Summary: Create Spring Boot examples and archetypes
 Key: CAMEL-8655
 URL: https://issues.apache.org/jira/browse/CAMEL-8655
 Project: Camel
  Issue Type: Task
  Components: camel-spring-boot
Reporter: Henryk Konsek
Assignee: Henryk Konsek


It would be nice with a camel-spring-boot example in 
https://github.com/apache/camel/tree/master/examples and an archetype 
https://github.com/apache/camel/tree/master/tooling/archetypes. I would love 
being able to demo using vanilla camel examples / archetypes and then run em 
with fabric8 / docker easily. And then having those examples will help on the 
camel microservice story.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8532) Spring Boot applications should block the main thread of the execution

2015-04-16 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497656#comment-14497656
 ] 

Henryk Konsek commented on CAMEL-8532:
--

Backported to 2.15.2 in commit ff554c053f9532d57037066564c029f8a6747c0d. Enjoy 
:) .

 Spring Boot applications should block the main thread of the execution
 --

 Key: CAMEL-8532
 URL: https://issues.apache.org/jira/browse/CAMEL-8532
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 Bootified Camel routers are supposed to block the main thread of the 
 application, so even for the empty router folks should be able to just 
 execute `java -jar myapp.jar` and the application will wait for the Ctrl+C.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8532) Spring Boot applications should block the main thread of the execution

2015-04-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8532:
-
Fix Version/s: 2.15.2

 Spring Boot applications should block the main thread of the execution
 --

 Key: CAMEL-8532
 URL: https://issues.apache.org/jira/browse/CAMEL-8532
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 Bootified Camel routers are supposed to block the main thread of the 
 application, so even for the empty router folks should be able to just 
 execute `java -jar myapp.jar` and the application will wait for the Ctrl+C.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8373) rest-dsl - CORS may have issue with non simple requests

2015-04-16 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497868#comment-14497868
 ] 

Henryk Konsek commented on CAMEL-8373:
--

Hi,

I have merged Stijn's pull request into the CAMEL-8645. Great thanks Stijn! It 
still doesn't resolve the main issue discusses here, but it allows to provide a 
workaround for Netty REST endpoints.

Cheers!

 rest-dsl - CORS may have issue with non simple requests
 ---

 Key: CAMEL-8373
 URL: https://issues.apache.org/jira/browse/CAMEL-8373
 Project: Camel
  Issue Type: Task
  Components: camel-core
Affects Versions: 2.14.1
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 2.15.2, 2.16.0


 Look into reported on SO
 http://stackoverflow.com/questions/28562817/camel-rest-dsl-enablecors-only-working-for-get
 For non simple requests, such as PUT see
 http://www.w3.org/TR/cors/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8645) Camel Netty component should not intercept consumers with httpMethodRestrict=OPTIONS

2015-04-16 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14497864#comment-14497864
 ] 

Henryk Konsek commented on CAMEL-8645:
--

Resolved in ca1aaa1b292ac7275853f2f27e6c5f7d5de618ac. Many thanks for 
@stijnvanbael for the patch!

 Camel Netty component should not intercept consumers with 
 httpMethodRestrict=OPTIONS
 

 Key: CAMEL-8645
 URL: https://issues.apache.org/jira/browse/CAMEL-8645
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 {{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
 This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
 {{OPTIONS}}, we Netty should allow to override the default responses.
 For example 
 {{from(netty4-http:http://0.0.0.0:8080/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
  should return the {{foo}} response to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8645) Camel Netty component should not intercept consumers with httpMethodRestrict=OPTIONS

2015-04-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8645.
--
Resolution: Fixed

 Camel Netty component should not intercept consumers with 
 httpMethodRestrict=OPTIONS
 

 Key: CAMEL-8645
 URL: https://issues.apache.org/jira/browse/CAMEL-8645
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 {{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
 This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
 {{OPTIONS}}, we Netty should allow to override the default responses.
 For example 
 {{from(netty4-http:http://0.0.0.0:8080/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
  should return the {{foo}} response to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-8645) Camel Netty component should not intercept consumers with httpMethodRestrict=OPTIONS

2015-04-16 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek updated CAMEL-8645:
-
Description: 
{{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
{{OPTIONS}}, we Netty should allow to override the default responses.

For example 
{{from(netty4-http:http://0.0.0.0:8080/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
 should return the {{foo}} response to the client.

  was:
{{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
{{OPTIONS}}, we Netty should allow to override the default responses.

For example 
{{from(netty4-http:http://0.0.0.0:{{port}}/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
 should return the {{foo}} response to the client.


 Camel Netty component should not intercept consumers with 
 httpMethodRestrict=OPTIONS
 

 Key: CAMEL-8645
 URL: https://issues.apache.org/jira/browse/CAMEL-8645
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


 {{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
 This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
 {{OPTIONS}}, we Netty should allow to override the default responses.
 For example 
 {{from(netty4-http:http://0.0.0.0:8080/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
  should return the {{foo}} response to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8645) Camel Netty component should not intercept consumers with httpMethodRestrict=OPTIONS

2015-04-16 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8645:


 Summary: Camel Netty component should not intercept consumers with 
httpMethodRestrict=OPTIONS
 Key: CAMEL-8645
 URL: https://issues.apache.org/jira/browse/CAMEL-8645
 Project: Camel
  Issue Type: Improvement
Affects Versions: 2.15.1
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.15.2, 2.16.0


{{HttpServerChannelHandler}} tries to provide default {{OPTIONS}} responses. 
This is nice feature, but if the {{httpMethodRestrict}} is explicitly set to 
{{OPTIONS}}, we Netty should allow to override the default responses.

For example 
{{from(netty4-http:http://0.0.0.0:{{port}}/foo?httpMethodRestrict=OPTIONS;).setBody().constant(foo!)}}
 should return the {{foo}} response to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8532) Spring Boot applications should block the main thread of the execution

2015-04-15 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496870#comment-14496870
 ] 

Henryk Konsek commented on CAMEL-8532:
--

It this concerns you, then I can backport my fix to the Camel 2.15.2 :) I will 
do it tomorrow.

 Spring Boot applications should block the main thread of the execution
 --

 Key: CAMEL-8532
 URL: https://issues.apache.org/jira/browse/CAMEL-8532
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Bootified Camel routers are supposed to block the main thread of the 
 application, so even for the empty router folks should be able to just 
 execute `java -jar myapp.jar` and the application will wait for the Ctrl+C.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8532) Spring Boot applications should block the main thread of the execution

2015-04-15 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496729#comment-14496729
 ] 

Henryk Konsek commented on CAMEL-8532:
--

Hi,

Just add spring-boot-starter-web to your project. It will block the main 
thread. Or camel-boot-starter-remote-shell. I didn't backported CAMEL-8532 
because it is as easy to block the main thread. I personally always add 
spring-boot-starter-web to the app to have a Jolokia endpoint exposed. 

I hope that resolves the issue. :)

Cheers.

 Spring Boot applications should block the main thread of the execution
 --

 Key: CAMEL-8532
 URL: https://issues.apache.org/jira/browse/CAMEL-8532
 Project: Camel
  Issue Type: Improvement
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Bootified Camel routers are supposed to block the main thread of the 
 application, so even for the empty router folks should be able to just 
 execute `java -jar myapp.jar` and the application will wait for the Ctrl+C.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-04-09 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14488188#comment-14488188
 ] 

Henryk Konsek commented on CAMEL-8554:
--

I've added some extra exclusions to the converter (Numbers and primitives). Now 
I will the option to provide custom mapper via registry.

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-04-09 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14488230#comment-14488230
 ] 

Henryk Konsek commented on CAMEL-8554:
--

Done. I need some docs and we can close this one.

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (CAMEL-8570) NullPointerException when using CXF-component in a spring-boot application with loglevel = INFO

2015-04-09 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek reassigned CAMEL-8570:


Assignee: Henryk Konsek

I will take a look at this.

 NullPointerException when using CXF-component in a spring-boot application 
 with loglevel = INFO
 

 Key: CAMEL-8570
 URL: https://issues.apache.org/jira/browse/CAMEL-8570
 Project: Camel
  Issue Type: Bug
  Components: camel-core, camel-cxf, camel-spring-boot
Affects Versions: 2.15.0, 2.15.1
Reporter: Jakob Thun
Assignee: Henryk Konsek
Priority: Minor
 Fix For: 2.16.0


 I get a NullPointerException when using log-level INFO or finer in a 
 spring-boot application with CXF. 
 The exception is thrown from DefaultCamelContext.java:2449, where it tries to 
 log how many routes have been started.
 I have made an example project to reproduce it, it's available here: 
 https://github.com/jakobthun/spring-boot-camel-cxf-logging-bug
 I have tried with camel version: 2.15.0  2.15-SNAPSHOT. Both have the same 
 behaviour.
 +Andrew Block started som analysis:+
 It is running into issues in this code block which is executed at logging 
 level = INFO 
 if (log.isInfoEnabled()) { 
 // count how many routes are actually started 
 int started = 0; 
 for (Route route : getRoutes()) { 
 if (getRouteStatus(route.getId()).isStarted()) { 
 started++; 
 } 
 } 
 log.info(Total  + getRoutes().size() +  routes, of which  + 
 started +  is started.); 
 log.info(Apache Camel  + getVersion() +  (CamelContext:  + 
 getName() + ) started in  + TimeUtils.printDuration(stopWatch.taken())); 
 } 
 The exception occurs when the status for the route is pulled from the route 
 service. It is null and the exception is thrown. The route is initially spun 
 up but then refreshes when the CXF consumer is initialized. 
 Swapping it to test with a direct consumer does not result in a similar 
 situation and startup succeeds at all logging level. 
 It appears the route is not being registered with the route service



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8567) New camel-raspberry component

2015-04-01 Thread Henryk Konsek (JIRA)

[
https://issues.apache.org/jira/browse/CAMEL-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14390332#comment-14390332
]

Henryk Konsek commented on CAMEL-8567:
--

Hi Greg,

Yay! I planned to create such component by myself! Great to see you were faster
:) .

I've been a bit sick recently, but now I'm getting back to work. I will review
it and merge into master soon.

Thanks again. Laters!

New camel-raspberry component
-

Key: CAMEL-8567
URL: https://issues.apache.org/jira/browse/CAMEL-8567
Project: Camel
Issue Type: New Feature
Affects Versions: 2.16.0
Environment: Linux and Raspberry Pi Raspbian
Reporter: Greg A.
Priority: Minor
Labels: GPIO, I/O, RasberryPi, component, features
Fix For: 2.16.0

Attachments: camel-raspberry.patch

I've started a new component to interface with an RaspberryPI.
I think it could be very interesting component to have for camel.
With this first version you manage all GPIO for Model A, A+, B, B+, 2B
Features
- input / ouput digital pin management
* with TOGGLE, LOW, HIGH action
* from(rbpi://pin?id=2mode=inputstate=HIGH) -- send new msg when HIGH
* to(rbpi://pin?id=9mode=outputstate=LOWaction=HIGH) -- when receive
msg set to HIGH
- input / ouput analog pin management
* for double value
* rbpi://pin?id=1mode=analog_input
- input / ouput pwn pin
* for int value
* rbpi://pin?id=1mode=pwm_input
I also developed an CamelMain stuff to test it very quickly on a Raspberry Pi.
One input - log - one output, stay tuned !!!
I've also create a mock to emulate RBPI on my Mac
Pi4j uses ASF : http://pi4j.com/license.html
Pi4j is OSGi compliant
but I don't know if component is correctly OSGi compliant
I am writing an documentation too.
TODO :
- smarter URI style like rbpi://pin/1/mode?[options]
- output endpoint with dynamic PIN
- GUI GPIO emulator
- i2c integration
- spi integration

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-03-28 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385441#comment-14385441
 ] 

Henryk Konsek commented on CAMEL-8554:
--

Sorry for all those duplicated cases. I got a network problems and I wan't 
aware I create all of them.

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-03-28 Thread Henryk Konsek (JIRA)


[ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385443#comment-14385443
 ] 

Henryk Konsek commented on CAMEL-8554:
--

Actually I think that we should keep this converter, but exclude String 
conversions from its scope. It's really pain in the ass not to have Map = 
Object POJO fallback converter in Camel. This is really common conversion and 
believe we should support it.

I propose then to:
- keep the conversion
- exclude some common non-Pojo types from it (String, Number, primitives)
- add option to lookup for the ObjectMapper in the registry, so people can 
provide their own preconfigured instances

What do you think? 

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8549) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8549:


 Summary: camel-jackson should provide Map = Object converter
 Key: CAMEL-8549
 URL: https://issues.apache.org/jira/browse/CAMEL-8549
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be 
nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8550) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8550:


 Summary: camel-jackson should provide Map = Object converter
 Key: CAMEL-8550
 URL: https://issues.apache.org/jira/browse/CAMEL-8550
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be 
nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8553) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8553:


 Summary: camel-jackson should provide Map = Object converter
 Key: CAMEL-8553
 URL: https://issues.apache.org/jira/browse/CAMEL-8553
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be 
nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8552) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8552:


 Summary: camel-jackson should provide Map = Object converter
 Key: CAMEL-8552
 URL: https://issues.apache.org/jira/browse/CAMEL-8552
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be 
nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)

Henryk Konsek created CAMEL-8554:


 Summary: camel-jackson should provide Map = Object converter
 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would be 
nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CAMEL-8554) camel-jackson should provide Map = Object converter

2015-03-26 Thread Henryk Konsek (JIRA)


 [ 
https://issues.apache.org/jira/browse/CAMEL-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henryk Konsek resolved CAMEL-8554.
--
Resolution: Fixed

Resolved in 2fa60111add917affc161570892efda4a763f56a.

 camel-jackson should provide Map = Object converter
 

 Key: CAMEL-8554
 URL: https://issues.apache.org/jira/browse/CAMEL-8554
 Project: Camel
  Issue Type: Improvement
  Components: camel-jackson
Reporter: Henryk Konsek
Assignee: Henryk Konsek
 Fix For: 2.16.0


 Jackson's {{ObjectMapper}} can be used to convert {{Map}} to pojo. It would 
 be nice if Jackson component provide this kind of fallback converter then.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

1 2 3 4 >

1 - 100 of 327 matches

Mail list logo