I have read seemingly every SO question response, and posted my own question
there that no one has answered up to this point, and I am about to tear my
hair out in frustration! :)
Using Camel Blueprint, v. 2.15.2, I have a route defined in the XML in which
I am attempting to set the CamelAwsSqsMes
It's working with a lazy init of the salesforce component in the route. I
couldn't get the camel context to recognize that the component was added in
main or in the route builder, but it works from a processor in the route. In
the processor the component has to be created with the camel context fro
If you just set transacted=true on a JMS route then the ACK mode is TX
and hence the message is not lost in case of an exception during
routing, as the ACK is deferred until the end.
But if you want to both consume and send to JMS queues in the same TX,
you need all that glory TX setup. And also i
Hi Jimmy,
If you would like to provide different destination resolvers for different
environments, use Spring Boot conditionals. For example:
@ConditionalOnProperty(name = "env", matchIfMissing = true)
@Bean(name="wmq")
DestinationResolver devdestinationResolver() {...}
@ConditionalOnProperty(na
In Camel 2.16 the simple language is supported in the message, so you can do:
.throwException(IllegalArgumentException.class, "Darn ${body} is
invalid")
In older releases you can not, and instead you can use a processor or
bean to throw the exception
On Fri, Sep 25, 2015 at 5:06 PM, james555
Hello,
i would like to print the value of a exchangeProperty in a
throwException-Clause like this (Camel 2.15.3):
public void configure() throws Exception {
from("direct:start")
.setProperty("propertyX", constant(true))
.setPr
Hi,
I have a program which creates Camel routes dynamically based on one or more
route xml files in a folder. You can also specify a context, which then will
lead to the route created in that specified camel context.
Basically this:
CamelContext camelContext = new SpringCamelContext(applicati
Hi,
if I send a message to an ActiveMQ broker directly (without camel) this is
extremly fast (<1ms). When sending messages in a camel route using the JMS
endpoint it is extremly slow (> 1 sec) every x messages.
Here is an example output of the provided test:
sending took 81ms
sending took 1081ms
Has nothing to do with Camel.
There is only a single instance of listItem created. In the for loops, this
single instance is emptied (listItem.clear()) and repeatedly added to the
listOfRecords.
Replace listItem.clear() with listItem = new ArrayList() and see what
happens.
On Fri, Sep 25, 2015 a
Hi
Yeah sure if its CXF 3.1.x that are jackson 2.4.x I think we can set
the osgi range of camel-swagger-java to be compatible. It would after
all be great if we get this working on karaf and potential with
camel-cxfrs or CXF-RS being able to leverage this too.
On Fri, Sep 25, 2015 at 2:48 PM, A
I just found out - after reading a little in "Camel In Action" ;-) - that I
could use this:
org.apache.camel.builder.script.ScriptEvaluationException
true
Mayby that is sufficient in my case. This exception would probably only
occur in my "javascript"(?)
-
thanks.
2015-09-25 14:56 GMT+02:00 Andrea Cosentino :
> I've upgraded Jackson to 2.6.2 while Claus was working on
> Camel-swagger-java.. I wasn't aware of this problem, but we can downgrade
> Jackson for the moment and bring it back to version 2.6.1.
> --Andrea Cosentino --
> On 25. sep. 2015, at 14.18, Henryk Konsek wrote:
>
> Hi Jimmy,
>
> If you would like to create a simple URI for the pre-configured component,
> then Claus suggestion to create a Spring bean with name/alias matching your
> target component, is a way to go. Register the pre-configured JMS compo
Hi,
I have a situation where I want to set some properties on my exchange, if it
is possible. But I dont want the exchange to fail, if the property is not
present. I have tried something like this:
request.body.substring(25, 33)
I've upgraded Jackson to 2.6.2 while Claus was working on Camel-swagger-java..
I wasn't aware of this problem, but we can downgrade Jackson for the moment and
bring it back to version 2.6.1.
--Andrea Cosentino -Apache Camel Committer
Email: ancosen1...@yahoo.com
Hi Claus,
The OSGi sample was included in CXF 3.1.3 and it uses this installer
description at the moment.
https://github.com/apache/cxf/blob/master/distribution/src/main/release/samples/jax_rs/description_swagger2_osgi/src/test/resources/features/features.xml
The same sample is also in 3.0.7-SNAPS
Hi Jimmy,
If you would like to create a simple URI for the pre-configured component,
then Claus suggestion to create a Spring bean with name/alias matching your
target component, is a way to go. Register the pre-configured JMS component
via:
@Bean(name = "wmq")
JmsComponent myWmqComponent() {
J
What version of CXF is that?
On Fri, Sep 25, 2015 at 1:05 PM, Aki Yoshida wrote:
> Hi Claus,
> Cool.
>
> I wanted to try it out on the Karaf setup that we have for CXF with
> swagger 1.5.4.
>
> Then I noticed that camel-swagger-java is asking for jackson [2.6,3).
> I am wondering if we could mak
> On 25. sep. 2015, at 12.00, Claus Ibsen wrote:
>
> Maybe an earlier callback can be added to CamelContextConfiguration?
>
> But instead of using that callback you can use some spring annotation
> that creates this component and name it wmq. Then Camel lookup in the
> spring bean registry for
Hi Claus,
Cool.
I wanted to try it out on the Karaf setup that we have for CXF with
swagger 1.5.4.
Then I noticed that camel-swagger-java is asking for jackson [2.6,3).
I am wondering if we could make it down to [2.4,3).
swagger itself is currently using 2.4.x and in the CXF's current Karaf
setu
Maybe an earlier callback can be added to CamelContextConfiguration?
But instead of using that callback you can use some spring annotation
that creates this component and name it wmq. Then Camel lookup in the
spring bean registry for "wmq" when it wants to use the component with
that name, and use
> On 25. sep. 2015, at 11.42, Claus Ibsen wrote:
>
> I would favor configuring this on the component and name it wmq, then
> the endpoints can be simply as you want.
>
> So maybe something with
>
> @Bean("wmq")
> JmsComponent myWmqComponent() {
> ...
> }
>
> Not sure what the spring annotatio
I would favor configuring this on the component and name it wmq, then
the endpoints can be simply as you want.
So maybe something with
@Bean("wmq")
JmsComponent myWmqComponent() {
...
}
Not sure what the spring annotation is for assigning a name.
On Fri, Sep 25, 2015 at 11:37 AM, Jimmy Selgen
> On 25. sep. 2015, at 11.28, Henryk Konsek wrote:
>
> from("jms:myqueue?destinationResolver=#myCustomDestinationResolver
> ").to(...);
This would of course solve the problem, but I’m trying to simplify things a bit
for my end users, so instead of the above, they can simply use
from(“wmq:que
Hi Jimmy,
You have to add it as a Spring (not Camel) bean:
@Bean
MQDestinationResolver myCustomDestinationResolver() {
return new MQDestinationResolver();
}
Then refer to it using "destinationResolver" option of the endpoint and
"hashtag" registry notation:
from("jms:myqueue?destinationReso
Hi
I’m working on a Spring Boot/Camel application, and need to setup a custom
MQDestinationResolver (WebSphere MQ).
I was doing this in CamelContextConfiguration.beforeApplicationStart, but the
deadLetterChannel resolves the channel at configuration time, and not at
startup time, so i need the
Hello guys
In my use case, I am getting 2 jdbc: component results in 2 headers namely
Q1_Resultset and Q2_Resultset. In my processor, I am trying to find the Join
of above 2 result sets as data are coming from different heterogenous
databases.
After calculating joins, I am adding each join row in
27 matches
Mail list logo
