[Camel] Camel integration in the Kura CloudService
See original GitHub issue@hekonsek this feature leverages the Kura multiple connections feature recently added on the develop branch.
You need to implement a new CloudServiceFactory and a component registering a CloudService in the OSGi framework.
The Camel implementations will be CamelCloudServiceFactory and CamelCloudService.
The Kura default implementation of the CloudServiceFactory can be used as a reference implementation.
Please note that the CloudService implementation must also be a Kura ConfigurableComponent so, in the case of the CamelCloudService, its configuration could be the Camel XML routes for that CloudService instance (the same configuration of the Camel quickstart example).
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (22 by maintainers)
Top Results From Across the Web
Kura/Camel Integration - Eclipsepedia
The Eclipse Kura development team is collaborating with the Apache Camel community to integrate the Apache Camel into Eclipse Kura.
Read more >Leveraging the power of Apache Camel in Eclipse Kura
This tutorial walks you through the Camel integration of Kura wires, which allows you to bridge both technologies, and leverage the power of ......
Read more >Kura Camel To/From Different Cloud Service Topics #1249
When creating a Kura Camel XML Router, I would like to create a "route" that listens on 1 Kura Cloud Service and publishes...
Read more >Kura - Apache Camel
This documentation page covers the integration options of Camel with the Eclipse Kura M2M gateway. The common reason to deploy Camel routes into...
Read more >Camel and Kura: Providing Telemetry Data as OPC UA - DZone
We will be configuring a new cloud service instance which takes Kura application payload data and provide it as OPC UA, using the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

What I mean is, that currently there is an interface
CloudServiceFactory, which is never used in the Web UI. The create commandkura.cloud:createConfiguration, which suggests being generic (by its naming) however is directly implemented byDefaultCloudServiceFactory, without using any interface. So the only possible way, as of now, is to make a complete manual implementation. Not using the interface and not using some sort of generic console command. And even after the creation, everything still has to be configured in a way that is not covered by the interfaces, but goes with theConfigurableComponentconstruct.Wouldn’t it make more sense to actually implement some sort of management service, hosting the configurations for different implementations and then leveraging the
CloudServiceFactoryto create instances based on those configurations. That way it would be possible to track the existing configurations (there would be some sort of status, even if the component did not register), there could be a state for missing components, …Or at least provide a console command or Web UI to support this new construct.
Yes. And #810 is merged now.