I am trying to make a rest call, via HTTPS and have 2way auth. I originally
tried to do this with CXF[1], but due to an issue with the conduit not
attaching, have moved to a jetty endpoint.
I have the below config for the jetty endpoint:
Thanks. Its just as important to know what is not there to keep from
spinning one's wheels. It seems reasonable to add functionality to the
file producer to perform platform independent delete operations on file
systems separately from writes though I don't know if this is exactly
what you were w
Hi
Ah we dont have that.
But we could add support for the file producer to support delete=true
so it will delete the file it wrote at the end of the UoW. But then
again it would only be for special use-cases where you need to write
temp files.
You can always write a bit of java code that deletes
Using Camel 2.15.1 and CXF 3.0.4 in a Karaf container, I'm wondering how
one can control the Spring version.
Camel feature "camel-spring" loads Spring with
spring
which will result in loading 3.2.11.RELEASE.
Is there a way to use Spring 4?
- Martin
Hey Guys,
I'm a newbie to Camel and self-taught in Java. I've been scouring the
internet and I hope you can point me in the right direction.
This is what I am trying to do:
(1) User hits a web service
(2) As a response the web service returns a webpage
I know I have to use HTTP and that the Je
Imagine that your FTP directory shows the "C:\Program Files" on Windows or
"/usr/lib" on Linux. There is a very large number of files. Files can not be
deleted.
Process periodically scans all files in all folders, filters, and sorts.
Uses a database table to store the names of files previously trea
Hi Akram,
I've started to work with the Elasticsearch component recently so I had a
look at it for you. It works correctly if you set the message headers.
I've debugged it and there is a bug in the ElasticsearchProducer:
https://github.com/apache/camel/blob/master/components/camel-elasticsearch/s
On the new version of Apache Camel 2.15.1 started to happen strange errors.
On this version 2.15.0 there is no error.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-ftp-2-15-1-return-ftp-error-code-421-tp5765272.html
Sent from the Camel - Users mailing list archive a
I just find the recent change[1] by using the "gitk components/camel-xmpp”
command.
The work around could be change the smack version to 4.0.6.
[1]https://issues.apache.org/jira/browse/CAMEL-8520
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (
No, I haven't, and you're right - I should have. I'm an easily distracted
type though and I'm trying to get some ZCL stuff pushed to maven central
asap. I use camel for a ton of testing of that kind of thing, and shortly
I'll be pushing out an xbee camel component I wrote (and am now testing).
S
Hi
Have you looked at the source code changes in camel-xmpp 2.15.0 and
2.15.1 and also about any JAR upgrades.
The best clue would be in any of those changes.
On Fri, Apr 3, 2015 at 12:18 PM, Christopher Piggott wrote:
> Hi,
>
> Earlier this evening I upgraded my camel project from 2.15.0 to 2.1
Hi,
Earlier this evening I upgraded my camel project from 2.15.0 to 2.15.1 with
no other code changes, and suddenly I was unable to connect to my XMPP
server. The error I got was roughly this:
"SASLauthentication failed using mechanism DIGEST-MD5:"
I did some brief troubleshooting but was not a
I forgot to mention. Version that I use is: 2.15.1
--
View this message in context:
http://camel.465427.n5.nabble.com/Conditional-skipping-when-intercepting-message-tp5765255p5765267.html
Sent from the Camel - Users mailing list archive at Nabble.com.
13 matches
Mail list logo