cation, i.e. deployed to Karaf, in case the previous blueprint unit
test code allowed something that would not work in deployed code. If I
continue to see that issue, I'll reopen a new issue.
Thanks,
Scott
On Sat, Sep 5, 2015 at 1:18 PM, Scott Cranton wrote:
> Looking closer at CamelBlue
My code from the Apache Camel Developer's Cookbook is now getting an error
trying to upgrade from Camel 2.15.2 to 2.15.3 around testing the Blueprint
Property / Test Support. This same code has worked fine over last 2 years
since version 2.12. With version 2.15.3, I'm seeing a runtime error
in
Cam
think the unit tests in the Camel source would also
fail then...
On Sat, Sep 5, 2015 at 1:02 PM, Scott Cranton wrote:
> My code from the Apache Camel Developer's Cookbook is now getting an error
> trying to upgrade from Camel 2.15.2 to 2.15.3 around testing the Blueprint
> Property /
Mayank,
What version of Camel are you running? Can you send your route snippet that
calls the camel-ssh component?
>From the log, it looks like it connected correctly, but there may not have
been a command to run in the body of the message or configured in the
endpoint URI...
Scott
On Thu, Nov
GVvenkat,
I'd be curious what your workaround is. Curious if there's a change needed
in camel-ssh to make it easier...
Scott
On Tue, Jun 4, 2013 at 3:04 PM, Gvvenkat wrote:
> I found a work around for this... Thanks, if anyone had spent any time on
> it.
>
>
>
>
> --
> View this message in co
Alan,
I haven't tried drools with camel and blueprint yet, but I do know
that they've made a bunch of osgi enhancements to drools in
6.0-SNAPSHOT. I was thinking of upgrading that camel drools example
(still with spring) to see if I could eliminate more of the uberjar
stuff...
You may want to try
b 15, 2013 at 9:33 PM, Scott Cranton wrote:
>> I've created an example showing camel-ssh deployed in Karaf using
>> classpath and file based public key security.
>>
>> https://github.com/scranton/example-security-camel-ssh
>>
>> I'll try to clean it u
ew example...
Then look to update the doc...
On Fri, Feb 15, 2013 at 6:53 AM, Scott Cranton wrote:
> Excellent! thanks for the QA ;-)
>
> The camel-ssh doc clearly needs help, so any thoughts you have on how
> to update based on your recent experience would be most appreciated...
>
>
hanks a lot guys.
>
>
> On Fri, Feb 15, 2013 at 11:34 AM, Scott Cranton wrote:
>
>> Have you tried setting the keyPairProvider to an instance of
>> org.apache.sshd.common.keyprovider.ResourceKeyPairProvider? That
>> should work better in OSGi, though I haven't
prefix, but no luck.
>>>>
>>>> The unit test works fine…problem is in the OSGi I guess…some classpath
>>>> issue? I don't know, I have quite a headache from this already, need a
>>>> break.
>>>>
>>>>
>>
I've just noticed the reference syntax that some components use, but
its not clear to me exactly how it works, and more importantly how new
components are supposed to use it correctly... I don't see any
documentation on it, and I've only found some mentions of it in the
JIRA where it was created an
Glad you figured it out. Yeah, the camel-ssh page does need some
attention. Thanks for the feedback, and I look forward to seeing your
suggested updates to the doc.
The certFilename is just a shorthand for creating a
FileKeyPairProvider, which is identical to what the
SshComponentSecurityTest is d
In creating unit tests for my Camel routes, I've tried to be
consistent with the Camel project's conventions figuring those are the
best practices, or at least the most tested path. I've noticed that
the vast majority of Camel unit tests use the
CamelTestSupport.getMockEndpoint(...) convenience met
Leandro,
from memory, I'm thinking having the leading @ -- ssh://@host:port -- is
causing you problems…
try
ssh://user01:My_pwd@10.54.139.52:6059?userFixedDelay=true&delay=5000&pollcommand=ls
and see if that works better…
Hope that helps,
Scott
On Jan 11, 2013, at 6:41 AM, Leandro Franchi w
14 matches
Mail list logo
