Re: interceptFrom and interceptSendToEndpoint not working

2017-07-17 Thread Claus Ibsen
Mind that the query parameters is sorted a..z by Camel, so if you have
more than one parameter then set your wildcard accordingly, or use a
regular expression syntax instead, which is also possible.
http://camel.apache.org/intercept



On Mon, Jul 17, 2017 at 4:47 AM, laiyhman  wrote:
> Hi,
>
> The following works
> rabbitmq:localhost/xxx*
>
> but anything with the "queue" like below does not work,
> rabbitmq:localhost/xxx?queue=*
> rabbitmq:localhost/xxx?queue=yyy*
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/interceptFrom-and-interceptSendToEndpoint-not-working-tp5807012p5807171.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2


Re: getResourceAsStream in OSGi bundle not working with Camel 2.19

2017-07-17 Thread rsteppac2
rsteppac2 wrote
> What I could do, I guess, is to wrap the library's factory code in my own
> and set the context classloader of the current thread to the application
> context class loader before delegating to the actual factory.

This worked. Though instead of the application classloader I used the
classloader of the factory class. 


Ralf



--
View this message in context: 
http://camel.465427.n5.nabble.com/getResourceAsStream-in-OSGi-bundle-not-working-with-Camel-2-19-tp5807017p5807197.html
Sent from the Camel - Users mailing list archive at Nabble.com.


RE: Problem with ssh under camel 2.19.0

2017-07-17 Thread Thibault, Daniel
-Message d'origine-
De : Claus Ibsen [mailto:claus.ib...@gmail.com] 
Envoyé : 16 juillet 2017 03:16
À : users@camel.apache.org
>
> You should use the versions of the JARs that Apache Camel is built with.
>
> When you use Maven you get this "for free" here is what camel-ssh has a 
> dependency:tree

A simple (but devastating) constraint I must operate under is that I cannot use 
Maven.

> [INFO] org.apache.camel:camel-ssh:jar:2.20.0-SNAPSHOT
> [INFO] +- org.apache.camel:camel-core:jar:2.20.0-SNAPSHOT:compile
> [INFO] |  \- org.slf4j:slf4j-api:jar:1.7.22:compile
> [INFO] +- org.apache.mina:mina-core:jar:2.0.16:compile
> [INFO] +- org.apache.sshd:sshd-core:jar:0.14.0:compile
> [INFO] +- org.bouncycastle:bcpg-jdk15on:jar:1.55:compile
> [INFO] |  \- org.bouncycastle:bcprov-jdk15on:jar:1.55:compile
> [INFO] +- org.bouncycastle:bcpkix-jdk15on:jar:1.55:compile
> [INFO] +- org.apache.camel:camel-test:jar:2.20.0-SNAPSHOT:test
> [INFO] |  \- junit:junit:jar:4.12:test
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test
> [INFO] +- org.apache.logging.log4j:log4j-api:jar:2.8.2:test
> [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.8.2:test
> [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.8.2:test
> [INFO] +- org.apache.camel:apt:jar:2.20.0-SNAPSHOT:provided
> [INFO] |  \- org.apache.camel:spi-annotations:jar:2.20.0-SNAPSHOT:provided
> [INFO] +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile
> [INFO] \- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile

Putting these in the class path does the trick:

camel-core-2.19.1.jar
camel-ssh-2.19.1.jar
slf4j-api-1.7.25.jar
slf4j-simple-1.7.25.jar
sshd-core-0.140.jar
bcpg-jdk15on-157.jar
bcpkix-jdk15on-157.jar
bcprov-jdk15on-157.jar

(The bouncycastle jars were obtained from 
https://www.bouncycastle.org/download/crypto-157.zip)

The remaining jars (mina-core-2.0.16, camel-test-2.20.0, junit-4.12, 
hamcrest-core-1.3, log4j-api-2.8.2, log4j-core-2.8.2, log4j-slf4j-impl-2.8.2, 
apt-2.20.0, spi-annotations-2.20.0, jaxb-core-2.2.11, jaxb-impl-2.2.11) may be 
needed if/when other features of camel get called upon, I guess.

I find it bizarre that Camel 2.19 would still rely on sshd-core-0.16.0 (dating 
back to early 2015) while sshd-core has moved on to 1.6.0. When will the 
migration occur?

On a different tack, the code yields in part this warning message:

[sshd-SshClient[5be46f9d]-nio2-thread-1] WARN 
org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at 
/: presented unverified EC key: ac:...:6a

Is there any way to get rid of this?  I'd have expected a known_hosts option 
for camel-ssh, but there isn't one.

Daniel U. Thibault, M.Sc.²
Computer Scientist, MCCS-SPC, Valcartier Research Centre Defence
Research and Development Canada / Government of Canada


Re: SFTP list of files

2017-07-17 Thread rwoolf
When you say "build your own java code that uses the ftp client to do your
own ftp 
login and listing" I'm a little unclear on what you mean.  Is there a way
for me to use the ftp component to help me with logging into the FTP
(actually an SFTP) site?  I'm thinking that this approach is what I will
need to do in the end, but I don't see how I can utilize the the ftp
component in my java code to achieve this.  Or are you meaning to use a
different client?



--
View this message in context: 
http://camel.465427.n5.nabble.com/SFTP-list-of-files-tp5805920p5807253.html
Sent from the Camel - Users mailing list archive at Nabble.com.


https4

2017-07-17 Thread Ryan T
I'm trying to connect to devices that have https enabled but you connect to
an ip address and no valid certificates.  How can I allow all certificates
using http4 endpoint?



Getting error:
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: No trusted certificate found

Additional Info:
Devices cannot communicate on http.  It has to be https.
I have no control over the certificates for the devices.



--
View this message in context: 
http://camel.465427.n5.nabble.com/https4-tp5807254.html
Sent from the Camel - Users mailing list archive at Nabble.com.