I'm trying to tap into an atom feed that is requiring the Accept request
header to either be application/xml or application/atom+xml.
Is there a way to limit the atom feed definition in the uri to specify only
those two values? Currently the default for the atom feed appears to be
Accept: text/h
I am using camel 2.15 and am seeing the following:
I've defined an mqtt route as follows:
mqtt:UnittestInputSecure?host=ssl://172.30.228.23:8883&userName=fred&password=derf&subscribeTopicNames=SecureUnitTestTopic
When the mqtt broker is down at 172.30.228.23 and I try to start up my
application,
I'm running camel 2.15.2 and have been performing some load tests on a jetty
consumer component with some POST requests.
My endpoint uri looks like this
jetty:http://0.0.0.0:8080/pe-eh/v1/event?httpMethodRestrict=POST&maxThreads=200&minThreads=5
I can consistently produce the stack trace seen
I am trying to consume email messages from a folder on a gmail.com account
using the following URI.
imaps://imap.gmail.com?consumer.delay=6&delete=false&folderName=camel&mapMailMessage=true&password=xx&peek=true&unseen=true&username=myu...@gmail.com
And I'm getting the following error:
W
That did the trick.
Thanks loads.
--
View this message in context:
http://camel.465427.n5.nabble.com/org-apache-camel-FailedToCreateRouteException-Failed-to-create-route-with-SNMP-component-tp5768341p5770704.html
Sent from the Camel - Users mailing list archive at Nabble.com.
It's actually weirder than first appeared.
I do have camel-snmp included in the pom.xml file. I should have mentioned
that in my original post.
I'm beginning to think it's a classloader issue... Oh joy..
Because everything works fine when I run the application within IntelliJ.
But when I make it
I'm using Camel 2.15.2 and suddenly find that context.addRoutes() is throwing
the following exception.
org.apache.camel.FailedToCreateRouteException: Failed to create route
SNMPPoll:udp:172.30.227.153:1.3.6.1.4.1.17491.1.1.2.1.2.201:
Route(SNMPPoll:udp:172.30.227.153:1.3.6.1.4.1.17491.1.1.2.1
Spoke too soon. It should look something like this:
--
View this message in context:
http://camel.465427.n5.nabble.com/https4-2-15-2-not-recognizing-my-httpClientConfigurer-endpoint-option-tp5767922p5768073.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I think I finally have it working. Not certain it's the ideal solution. But
it works and it took me a long time navigating through the debugger to
figure things out.
My route definition was then
from("direct:start").transform(simple("FRED")).to("https4://172.30.228.23:8444/InformaCast/RESTServi
My class that implements HttpClientConfigurer now looks like this from your
suggestions: and it still doesn't work.
My createRegistry() looks like this:
@Override
I added a jndi.properties file that looks like this:
My uri now looks like this
https4://172.30.228.23:8444/InformaCast/REST
This still isn't working. It is as though it isn't recognizing my registry
during runtime.
In my unit test I've overrided createRegistry() because I'm not using spring
as your example solution does.
@Override
protected JndiRegistry createRegistry() throws Exception {
JndiRegistry
Like several similar posts I've seen I need to allow self-signed certs for
https4 (2.15.2). Mine isn't working.
I've created an implementation of HttpClientConfigurer that allows any
host/cert. Below is the implementation of configureHttpClient().
@Override
public void configureHttpClien
12 matches
Mail list logo
