Hi,
It looks like you have incompatible Servlet API jars included in your WAR.
So your jars do not match the API used by your Tomcat.
Cheers!
czw., 25.06.2015 o 19:11 użytkownik Tim Dudgeon
napisał:
> I'm trying to run some routes in tomcat using the servlet component
> (CamelHttpTransportServ
Hi,
I noticed that method parameters passed in to an EJB's method via
@ExchangeProperty or @Properties is always null when the EJB is created by a
different war file. If, on the other hand, I do the method parameter mapping
explicitly within the route, all works just fine. Is this by design or did
Hi,
I’m currently evaluating the RestDSL, and I do not see any handling for query
parameters. Just like I can define my in- and out-coming types I would have
expected to find something similar to define the (optional) parameters of the
querystring so that i.e. swagger could read and automatical
Hi,
Hopefully an easy one to answer but I've been unable to find the answer
myself. I've created a test class that extends CamelTestSupport. I have a
POJO class with a method that is annotated with
@Consume(uri="direct:someEndpoint"). The problem is that when I use a
producer template in my uni
An improvement documented in CAMEL-7936 describes the exact situation you
describe. Work is on the way for support of this feature
Query parameters are available as header values so they can be used in your
route currently, so the declaration of header values functionality should be in
there so
ConsumersCount is amount of kafka.consumer.Consumer instances.
consumerStreams is amount of kafka.consumer.KafkaStream instances.
https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Example
http://ingest.tips/2014/10/12/kafka-high-level-consumer-frequently-missing-pieces/
--
View t
Yes, seems so. I fixed it by managing the dependencies, but what was
happening made no sense to me as two seemingly "identical" setups
behaved differently.
Tim
On 26/06/2015 11:21, Henryk Konsek wrote:
Hi,
It looks like you have incompatible Servlet API jars included in your WAR.
So your jar
Good day -
I am trying to port a production server's test suite to use ActiveMQ
(5.7.0.fuse-71-047) , where the
production server normally uses a licensed copy of SwiftMQ-HA , with
apache-camel-2.9.0.fuse-7-061 and
Spring Framework ( 3.1.2-RELEASE ) - us developers do not get access to
SwiftM
In an app I’m working on we have a need to make sure that all
CamelContext’s have some default configurations on them. We are using
CamelConfiguration. It would be best in our case if we could do this
configuration though spring. This is what I did after looking for an
existing solution.
I defin
