Try with latest release also.
And yeah contributions is welcome. You can try improving that component.
http://camel.apache.org/contributing
On Tue, Mar 28, 2017 at 2:35 PM, Oliver Wulff wrote:
> Even when there is no change in the file it starts parsing it from the first
> line every second:
>
So from what I observed, toD() creates multiple enpoints for the same route.
If I remove the endpoints and then add the route definition again, I can use
the updated HttpClientConfigurer instance without having to create new
component.
> You need to define a new http4 component if you have differ
Hi,
I don't know much about Redis though, it seems the PSUBSCRIBE and SUBSCRIBE are
the only two supported for consumer.
https://github.com/apache/camel/blob/master/components/camel-spring-redis/src/main/java/org/apache/camel/component/redis/RedisConsumer.java#L54
You may want to file a JIRA fo
According to the log you are not receiving the out message in time so it
times out.
Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message
was not received within: 3 millis.
Exchange[ID-mid1-34304-1490639453105-0-772494]
On Wed, Mar 29, 2017 at 12:04 AM, Ryan T [via Camel] <
Hi,
For what purpose you need to do that? It's possible to make a dirty hack like
this though
SpringCamelContext context = (SpringCamelContext)context;
context.setRegistry(new My CustomCompositeRegistry(context.getRegistry()));
I don't know if it really works or not. Note that the
ApplicationC
Found the ticket. FWIW okhttp dependency is already there for the unit tests in
camel-jetty9.
https://issues.apache.org/jira/browse/CAMEL-9268
I just assigned to myself in case I have spare time, but it would be great if
anyone else could make it before me.
Thanks,
Tomo
On 03/29/2017 02:52 AM
can anyone help me on diagnosing this exception? Any hints as to how I might
proceed on fixing it?
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-diagnosing-camel-exception-tp5796669.html
Sent from the Camel - Users mailing list archive at Nabble.com.
OK, so its not the XSLT
If i use the FILE uri to start the route the xml file is processed correctly
with XSLT URI and all the elements and values are correctly populated and
displayed.
BUT I was receiving the message using servlet and the body is of type
"text/plain"
I have been playing wit
I am looking at the documentation and examples and have been testing with
the Redis component. It seems that the only command that will work in a
consumer URI is SUBSCRIBE and PSUBSCRIBE . It seems that only works with
PUBLISH. Pub/Sub in REDIS is not persistent. I need something that is. If
i pu
I was thinking it was more of a problem related to toD() rather than http4
component. That's because when I use to() for creating http4 endpoint, I am
able to change the instance of HttpClientConfigurer easily at runtime.
Anyways, using the way you're suggesting, i.e., creating new http4
component
btw http4 is not the most easy http client to use and configure.
I would love if we get a new camel http component based on okhttp.
https://square.github.io/okhttp/
There should be a JIRA about this at Apache Camel.
On Tue, Mar 28, 2017 at 7:31 PM, Claus Ibsen wrote:
> You need to define a ne
You need to define a new http4 component if you have different client
configurer. It can only use one, and the first one created.
So create a new component with a different name, such as http4-foo,
http4-bar etc.
You can register new components in camel
context.addComponent("http4-foo", new Http
Even when there is no change in the file it starts parsing it from the first
line every second:
I use Camel version 2.16.3.
Maybe an option in Camel could be to use the Apache Commons IO Tailer
implementation similar to Apache Karaf Decanter here:
https://github.com/apache/karaf-decanter/
I know we can add Simple Registry to camel context using this-
CamelContext camelContext = new DefaultCamelContext(SimpleRegistry.class);
But, is there a way to add SimpleRegistry other than the way mentioned
above? I ask because my camel context is initialized by Spring.
--
View this message
Thanks for a quick response,
Will have a look at this and see if I make it resolve that dependency.
However as I wrote the same tests work and completes successfully locally
and there the same ERROR message is logged.
So it seems that it's not vital for the tests to complete. Well at least
not wh
Not sure but from the log:
ERROR: Bundle org.apache.camel.karaf.camel-karaf-commands [61] Error
starting mvn:org.apache.camel.karaf/camel-karaf-commands/2.18.0
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.camel.karaf.camel-karaf-commands [61]: Unable to resolve
6
Hello,
Trying to blow some life into the camel-extra project and get a 2.18.x
release out.
However the karaf integration tests keep failing on Jenkins[1] without any
clear indication on whats wrong. When I run locally the same maven build
passes with success.
A PR [2] or any other help would be m
Did you have a web service running on address: http://localhost:9090
/endpoint2 in the same JVM?
Regards,
/Joe
On Tue, Mar 28, 2017 at 8:01 AM, anirban.gupta4
wrote:
> Hi,
>
> I have exposed two webservices as CXF beans, below is the code
>
> address="http://localhost:9090/e
So apparently, got this to work by overriding the httpclientconfigurer
instance in SimpleRegistry and then adding the route again in CamelContext.
However, this way is not working if I keep the httpclientconfigurer instance
in spring bean registry.
--
View this message in context:
http://camel.
Hi,
I have exposed two webservices as CXF beans, below is the code
http://localhost:9090/endpoint1";
serviceClass="serviceClass1"
serviceName="tns:serviceName1"
endpointName="tns:endpointName1"
wsdlURL="wsdl/WSDL1.wsdl"
Hi,
I created the CamelRoute below. The problem is that I always get an error at
the end of the process. All steps seem to work fine, but the last step fails
and I get a soapfault in soapui saying:
Part {http://javainuse.com}out should be of type
com.javainuse.OutputSOATest, not javax.xml.trans
21 matches
Mail list logo
