Whoever is facing this problem and cannot use async schedulling because the
endpoint is transacted, I've came up with a workaround, in my case I'm using
RabbitMQ as the from Endpoint:
This is my route configuration:
from(fromEndpoint) // AMQP INPUT QUEUE
.routeId(consumerRoute
Hi,
I have created a blueprint definition with a REST web service component in
the src/main/resources/OSGI-INF/blueprint folder.
It works fine when deployed in the Karaf OSGI platform.
It was all good until I started to unit test the route. The junit complains
about bean not found RestConsumerF
Hi,
I am using SQL JDBC with Camel blueprint XML.I am new of blue print XML. I
want to stream the JDBC resultSet database by
using blueprint XML. Could you please suggest the solution.
The below is the select statement and currently reading from database
readSize is "25000"
how to stream the
Hi,
I am using SQL JDBC with Camel blueprint XML.I am new of blue print XML. I
want to stream the JDBC resultSet database by
using blueprint XML. Could you please suggest the solution.
The below is the select statement and currently reading from database
readSize is "25000"
how to stream the
Hi,
Have you checked CamelSpringTestSupport?
http://camel.apache.org/spring-testing.html
You can specify the Camel context XML under test by simply overriding the
createApplicationContext method:
protected AbstractXmlApplicationContext createApplicationContext() {
return new
ClassPat
Hi Debraj,
Then why can you not define jsonRPCProcessor in camelContext.xml instead of
blueprint.xml? If this processor depends on a specific producer template
("myTemplate") == Camel context, then I see no reasons this producer can be
shared across multiple Camel contexts.
On Tue, Jul 5, 2016 a
I actually used to use CXFRS in this application (you can still see
remnants of it like using the header "operationName" to route from a REST
endpoint to an ActiveMQ queue). Even if I used an immutable bean in the
header, that bean could still be replaced. It seems like the only way to
implement a
I've always used CXFRS so don't have any experience with the REST DSL
itself. With CXFRS I usually end up binding everything to the data object
when it first comes in and that does remain immutable so I don't end up
working with headers for any data elements. By using the same interface for
both my
Hello,
I have a Graphite server running and tested.
camel-example-spring-boot-metrics' Application.java settings are correct
for my installation.
When I run the example and look at the Graphite dashboard, I don't see any
metrics related to camel-example-spring-boot-metrics. Where should I look?
Let me give a more specific use case. Path parameters from rest-dsl are
passed in as message headers. I don't want any route to accidentally
overwrite or modify those headers as they're useful for the entire
lifecycle of that message.
On 5 July 2016 at 16:00, Matt Sicker wrote:
> The exact use c
The exact use case is preventing developers from [inadvertently] modifying
headers or properties that are used before and after a particular subroute.
On 5 July 2016 at 15:57, souciance wrote:
> I guess the question is, why would different routes split over different
> bundles want to write over
I guess the question is, why would different routes split over different
bundles want to write over the same header/property? What's the case here?
Surely it cannot be just to prevent accidents by developers because what
would be their reason to write over that header?
I think it is better to agre
Please let me know if you think of anything!
On 5 July 2016 at 15:16, Brad Johnson wrote:
> I certainly understand the impulse and think it is spot on but can't think
> of how to do it with headers. Claim checks might work but they are really
> for reducing overhead of data and not for locking
I certainly understand the impulse and think it is spot on but can't think
of how to do it with headers. Claim checks might work but they are really
for reducing overhead of data and not for locking like that but that might
be a viable solution depending on the exact problem.
Thanks Matt, this is
My use case is basically to help prevent bugs where a header or exchange
property gets modified. Some of my routes in question branch out into
several different bundles, and it is difficult to enforce contracts that
way amongst several developers with varying levels of Camel expertise.
Similar to h
I need some assistance to make sure I'm on the right track. I think I'm very
close, but I have a couple of missing pieces.
I have the following SQL statement:
select ticket_date, ticket_nbr, line_nbr, item_desc, quantity
from tickets
I want to group these rows by ticket date, ticket nbr, and l
That's what I figured. I'd have to look at the Map implementation of the
exchange but as far as I know there isn't a way to make it a write once
only operation. It's just a map of some sort. There might be a way to do
it with transactions but I'm not an expert there. I generally use headers
but
I'm thinking of an idea to prevent a header from being modified by other
parts of the route. A sort of contract if you will.
On 5 July 2016 at 13:01, Brad Johnson wrote:
> Is there another part of your process that is specifically changing the
> header or are you more concerned about it being co
Is there another part of your process that is specifically changing the
header or are you more concerned about it being consistently there across
routes? Nothing will change it automatically if it is your header. I
don't remember the actual implementation but conceptually it is just a
hastable/ma
As in once I set the header, nothing can change the header during the
lifecycle of the message during a route. Same for an exchange property.
--
Matt Sicker
Thanks.
I have seen this link.
I had some doubts. I have camelcontext.xml which gets message from MQ and
transforms and sends to a webservice, gets a response and then transforms and
send back to another queue.
I can mock the end points and can assert based on conditions etc.
How to tell my te
http://camel.apache.org/testing.html
> -Original Message-
> From: Vanshul.Chawla [mailto:vanshul.cha...@target.com]
> Sent: Tuesday, July 05, 2016 10:08 AM
> To: users@camel.apache.org
> Subject: Unit test case for XML DSL context and routes
>
> Hello All,
>
> We have some Camel code whi
Hello All,
We have some Camel code which is written in XML DSL. We need to add unit test
cases for each context(multiple routes) . Could someone please give a lead to
how this can be achieved.
Vanshul
Yeah Tadayoshi. jsonRPCProcessor is using myTemplate as shown below:-
whereas myTemplate is defined in camelContext which in turn is using
jsonRPCProcessor as shown below:-
http://camel.apache.
Hi All,
I update my camel karaf feature from 2.16.3 to 2.17.1, and now I get the
following exception:
/org.apache.karaf.shell.support.MultiException: Error executing command on
bundles:
Error starting bundle 225: Uses constraint violation. Unable to resolve
resource org.apache.camel.camel
There is an example in the Camel in Action 2 book.
https://github.com/camelinaction/camelinaction2/tree/master/chapter10/jetty-rest-security-karaf
On Tue, Jul 5, 2016 at 10:18 AM, Satish Kumar Kesharwani
wrote:
> I am using Swagger and rest dsl to build an application. Need to implement
> Basic
I am using Swagger and rest dsl to build an application. Need to implement
Basic Auth.
how can i implement SSL/ Basic Auth for jetty component in blueprint xml?
.endpointProperty("sslKeystore", "/security/serverKey.jks") how i can
configure in blueprint.xml file.
--
View this message in context:
27 matches
Mail list logo
