The deprecation is in using setHeader with a String as the second argument:
.setHeader(FileComponent.HEADER_FILE_NAME, "agents.xml")
And indeed Willems suggestion fixes the warning:
.setHeader(FileComponent.HEADER_FILE_NAME, constant("agents.xml"))
Claus Ibsen-2 wrote:
>
> Hi
>
> What is the @
On Wed, Apr 22, 2009 at 11:43 PM, rsmith wrote:
>
> I'm evaluating Camel and ran into a test case where messages aren't being
> delivered to a component for some reason. Being new to Camel this is
> probably a case of my test routes not being set up correctly.
>
> Here is what I have:
>
>
On Wed, Apr 22, 2009 at 11:58 PM, ychawla wrote:
>
> Uh, nevermind. Looks like Camel 1.6.0 uses JUEL 2.1.0. I was using JUEL
> 2.1.1. This might be an issue if Camel upgrades to the next minor version
> release of JUEL.
Hi
Thanks for the update. Maybe we/you can report this issue to JUEL so
th
Uh, nevermind. Looks like Camel 1.6.0 uses JUEL 2.1.0. I was using JUEL
2.1.1. This might be an issue if Camel upgrades to the next minor version
release of JUEL.
Cheers,
Yogesh
ychawla wrote:
>
> Hello All,
> I am trying to evaluate a header in Camel 1.6.0 using EL expressions.
> Here is
Hello All,
I am trying to evaluate a header in Camel 1.6.0 using EL expressions. Here
is my expression:
${in.headers['MyHeader'].startsWith('fooBar')}
false
When I run this, I get an exception:
javax.el.MethodNotFoundException: Cannot resolve method 'startsWith' in
'
I'm evaluating Camel and ran into a test case where messages aren't being
delivered to a component for some reason. Being new to Camel this is
probably a case of my test routes not being set up correctly.
Here is what I have:
Hi
There will and are several solutions to your problem.
You can use a processor to call another "route" so to speak. And then
inspect the result, and decide what to do.
from (a) -> processor -> route after validation
And in the processor you can "call the other route and inspect the response"
On Apr 22, 2009, at 15:29 , James Strachan wrote:
2009/4/22 Peter Maas :
Hi,
is it possible the programmatically replace parts of a route (for
testing
purposes) to temporarily add processor in the middle of the route for
example? One case I (think) I need it for is for testing unexpected
Hello All,
I have a question about the usage of the content filter. I have a route
where I want to validate the message, but I only want to validate a certain
part of the message. I looked at the content filter pattern and it didn't
seem like Camel had much built in functionality there:
http://
Hi,
After dug the code of XQuery, and wrote a simple test, I found you can
get the header value like this.
I suppose you have set the in message header "foo" with the value of "bar"
You need to define the variable in your template file just like this,
then you can use this variable as your want.
Hi Everyone,
I have this question. I am now gonna do an integration involving MQ and it
is different from the other mq scenarios i've handled before.
Most of what i've handled before involved the request reply pattern which
can easily be done in mq via the correlation id scheme.
In this case, wha
2009/4/22 Hadrian Zbarcea :
> Hi Peter,
>
> Imho not easily, because there is no way today to identify/address a node in
> the AST.
You can use idOrCreate() method on a node; which lazily creates a
unique ID for a node if you've not manually given it one - this can be
used with any AST node or Rou
Hi Roger
Any news on this?
I am super busy at the moment so I havent had the time to help out.
On Mon, Apr 20, 2009 at 7:47 PM, rogster wrote:
>
> I need to access camel context header variables in my XQuery endpoint.
>
> So in my context file i do something to this effect:
>
> bar
>
>
>
Hi
What is the @deprecation?
On Wed, Apr 22, 2009 at 2:56 PM, Willem Jiang wrote:
> Hi
>
> You could use constant for this, just like this
> from("direct:start").
> setHeader("foo", constant("ABC")).
> to("mock:result");
>
> Willem
>
> G.J. van de Streek wrote:
>> Is there a way to use st
2009/4/22 Peter Maas :
> Hi,
>
> is it possible the programmatically replace parts of a route (for testing
> purposes) to temporarily add processor in the middle of the route for
> example? One case I (think) I need it for is for testing unexpected errors,
> I'd like to mimic this by 'injecting' a
I have created ticket CAMEL-1558
https://issues.apache.org/activemq/browse/CAMEL-1558
To improve the interceptor to allow to intercept per endpoint basis.
And James and I have also talked about a Around AOP concept
Something like:
around(foo).with(bar)
On Wed, Apr 22, 2009 at 3:24 PM, Hadria
Hi Peter,
Imho not easily, because there is no way today to identify/address a
node in the AST. I can think of two things that may work.
One is to sorta artificially split the route in two using a direct
endpoint:
from(x).somestuff().to("direct"a");
from("direct:a").restoftheroute();
and
Hi
You can use a mock endpoint in the route where you would like it to
throw an exception or not
and then use the mock api to attach an processor when an exchange arrives
from(a) - to(b) -> mock(m) -> to(d)
And in your unit test
MockEndpoint m ...
m.whenAnyExchangeArrives(new Processor()...
t
Hi
You could use constant for this, just like this
from("direct:start").
setHeader("foo", constant("ABC")).
to("mock:result");
Willem
G.J. van de Streek wrote:
> Is there a way to use string constants in the simple expression language. I
> am trying to fix a deprecation warning in:
>
>
Hi,
is it possible the programmatically replace parts of a route (for
testing purposes) to temporarily add processor in the middle of the
route for example? One case I (think) I need it for is for testing
unexpected errors, I'd like to mimic this by 'injecting' a processor
which throws a
Is there a way to use string constants in the simple expression language. I
am trying to fix a deprecation warning in:
from("direct:saveAgentsFile")
.setHeader(FileComponent.HEADER_FILE_NAME, "agents.xml")
.to("file:///Users/streekgj/Desktop/filestore/?appe
Thanks for helping me out with this one. I have now the workaround in place
and am able to stick to the Camel version that is shipped with ActiveMQ.
--
View this message in context:
http://www.nabble.com/usage-of-multicast-tp23163812p23174878.html
Sent from the Camel - Users (activemq) mailing l
I also added the test into Camel 1.x branch, the test result looks good.
We may fix this issue in camel 1.6 :)
Willem
Willem Jiang wrote:
> Yes, these two walk around are turning the input stream which set by the
> http client to a re-readable object.
>
> I just added a simple integration test[
Yes, these two walk around are turning the input stream which set by the
http client to a re-readable object.
I just added a simple integration test[1] in Camel 2.0 trunk, the test
shows you don't need any walk around in Camel 2.0 :)
[1] http://svn.apache.org/viewvc?rev=767403&view=rev
Willem
C
Hi
You can also use .convertBodyTo(String.class) instead of the JMS queue.
It will convert the payload from stream based into a String that
safely can be read multiple times.
You can also use byte[].class if you want to keep it as byte based.
On Wed, Apr 22, 2009 at 10:15 AM, G.J. van de Streek
I noticed, that if I insert a queue in the route and go from there, that it
works:
public void configure() {
from("timer://foo?fixedRate=true&delay=0&period=6")
.to("http://avisi.nl/integration/agents";)
.to("activemq:example.B");
from("ac
26 matches
Mail list logo
