Hi Tomas!
SNMP v3 has some differences regarding the message model [1]. Maybe you'll
need to adjust your route / processing to it, take a look into this answer
[2].
[1] - http://www.snmp.com/products/techinfo/secmodels.shtml
[2] -
https://stackoverflow.com/questions/47764846/camel-snmp-cant-resiv
Hi Thomas!
You're right. My intention was just to point out that duo to v3, other
aspects of the SNMP camel component interaction may change. I couldn't find
any tests with v3 [1], though. Maybe there's room for improvement or a bug
in the code.
Many thanks for your snippet, I'm going to run some
Hi Thomas!
Nice that you could handle it. Do you mind sending a PR to improve the
component [1]? Although some tests needed to make sure this behavior
remains the same with a single user scenario.
[1] - https://github.com/apache/camel/blob/master/CONTRIBUTING.md
Cheers!
Zanini
On Tue, Jan 9, 2
I've opened a JIRA [1] to follow up with this issue.
[1] - https://issues.apache.org/jira/browse/CAMEL-12132
Zanini
On Tue, Jan 9, 2018 at 10:52 AM, Ricardo Zanini
wrote:
> Hi Thomas!
>
> Nice that you could handle it. Do you mind sending a PR to improve the
> component [
https://github.com/m88i/camel-wordpress
[3] - https://woocommerce.com/
--
Ricardo Zanini
Hi Joery!
Anytime you see that the endpoint requires a bean reference, its indeed
referring to a bean in the registry [1], that's why it needs a "#". You're
right when you say that the docs may be more clear about it.
[1] - http://camel.apache.org/registry.html
Cheers!
Zanini
On Mon, Jan 29, 2
Hi Tom!
I don't think the component "camel-jdbc" supports any other type of named
parameter other than :?name. Looking at the code
(DefaultJdbcPrepareStatementStrategy) we see:
protected boolean hasNamedParameters(String query) {
NamedQueryParser parser = new NamedQueryParser(query);
Hi!
You mentioned templating system, so Velocity [1] comes to mind. Have you
tried that? I guess that should be simple mapping from JSON/XML to velocity
(and keeping your formmating).
[1] - http://camel.apache.org/velocity.html
Cheers!
On Mon, 25 Mar 2019 at 05:07 Riaan Annandale wrote:
> Hi
Hi!
There’s a property “clientProperties” in the rabbitmq component endpoint:
“Connection client properties (client info used in negotiating with the
server)”
I think that it does what you’re looking for.
If not you could try creating a custom ConnectionFactory.
[1] -
https://github.com/apac
os use cases to encourage the component usage.
Thanks again!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Fri, Jan 26, 2018 at 5:50 AM, Claus Ibsen wrote:
> Hi Ricardo
>
> Thanks for donating your work to the Apache Camel project. Its great
> to see its been just merged.
&
10 matches
Mail list logo
