Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAMEL-8567 New camel-raspberry component (1st version) #452

Closed
wants to merge 10 commits into from
Closed

CAMEL-8567 New camel-raspberry component (1st version) #452

wants to merge 10 commits into from

Conversation

gautric
Copy link
Contributor

@gautric gautric commented Mar 29, 2015

I've started a new component to interface with an RaspberryPI.
I think it could be very interesting component to include it.

@gautric
Copy link
Contributor Author

gautric commented Mar 30, 2015

@davsclaus : Pi4j has got an 1.0-RC, I will check with author when he can provide an 1.1 final version

@davsclaus
Copy link
Contributor

output endpoint with dynamic PIN rbpi://pin/{header.id}/mode?[options]

Are you referring to the header with key on the Camel message? If so see this FAQ
http://camel.apache.org/how-to-use-a-dynamic-uri-in-to.html

@davsclaus
Copy link
Contributor

smarter URI style like rbpi://pin/1/mode?[options] have you got a documentation to implement it correctly

Can you explain a bit more?

If you want /mode to be part of the context-path, then you need to map that in the component class. eg that is the remaining parameter in the create endpoint. That requires a bit more coding, but some components do that.

For example some of the HTTP related
https://github.com/apache/camel/blob/master/components/camel-ahc/src/main/java/org/apache/camel/component/ahc/AhcComponent.java#L57

And the JMS component uses the context-path to know what kind of jms queue/topic you are using
https://github.com/apache/camel/blob/master/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsComponent.java#L485

@gautric
Copy link
Contributor Author

gautric commented Mar 30, 2015

Everything should work fine, I've included all comments
Just standby for pi4j 1.0 final version

@hekonsek
Copy link
Contributor

hekonsek commented Apr 1, 2015

Yay! This is great stuff. I'll take a look at it in the coming days.

@hekonsek
Copy link
Contributor

Hi @gautric,

pi4j v1 is out. Can you include it in the project?

Also, can you create the documentation page for the component?

Cheers.

@hekonsek
Copy link
Contributor

BTW I love your blog post [1]. It will be nice if you can update it as soon as Camel RPi is in master. I'd like to promote this link a little bit then. It is worth wider attention.

[1] http://gautric.github.io/blog/2015/04/03/apache-camel-raspberrypi-integration.html

@hekonsek
Copy link
Contributor

One more question - do have to install pi4j on the target device? Can't we just put pi4j jar into the the fat jar and then push it into the device? That would be easier from the deployment/demo point of view.

@hekonsek
Copy link
Contributor

@gautric Hi Greg, any updates on this?

@davsclaus
Copy link
Contributor

This component cannot be hosted at ASF. @gautric do you mind closing this ticket.

@davsclaus
Copy link
Contributor

@gautric do you mind closing this PR?

@gautric gautric closed this Apr 22, 2015
tdiesler pushed a commit to tdiesler/camel that referenced this pull request Feb 20, 2019
[ENTESB-9229] Upgrade to bouncycastle 1.60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants