You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "jason.parr" <ja...@usa.net> on 2011/08/10 10:36:56 UTC
Stubbing jms with an inprocess transport when using
CamelTestSupport
Hi,
I want to test my 'production' route unchanged using CamelTestSupport.
As show in the doco I stub out jms component with an inprocess trasnport say
seda:
@Override
protected CamelContext createCamelContext() throws Exception {
CamelContext context = super.createCamelContext();
context.addComponent("jms", context.getComponent("seda"));
...
This works fine until any of my jms endpoints in the 'production' route have
jms specific parameter, e.g.
from("direct:tradebus-trades")
.to("jms:topic:NOMURA.FIET.STP.RADIAL.TRADES?&disableReplyTo=true");
When I run my test I now get:
org.apache.camel.FailedToCreateRouteException: ... There are 1 parameters
that couldn't be set on the endpoint. Check the uri if the parameters are
spelt correctly and that they are properties of the endpoint. Unknown
parameters=[{disableReplyTo=true}]
What's the best way of replacing jms with an inprocess transport without
having to change the original route?
In my test I add an extra a file endpoint to play messages into the original
route, which seems to work fine.
@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RadialRouteBuilder() {
@Override
public void configure() {
super.configure();
from("file:src/test/data/radial-route-builder-test-case?noop=true&include=bond_msg.*")
.to("jms:queue:nomura.fiet.stp.bloomberg.bond-trades");
Thanks
--
View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p4685084.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using
CamelTestSupport
Posted by smadarapu <sr...@adp.com>.
Wow, yes that worked. I misunderstood after your first reply, second one
clarified it.
I had this initially, with the endpoint URI being *"jms:queue1:msgs"*
context.addComponent("jms", context.getComponent(*"seda"*));
after first reply i changed the URI to be *"stub:jms:queue1:msgs"* which
worked but after your second reply, i changed by URI back to original and
context.addComponent("jms", context.getComponent(*"stub"*));
Now this is working, thanks for the tip, its great.
--
View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p5744965.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using CamelTestSupport
Posted by Claus Ibsen <cl...@gmail.com>.
Yes stub is like seda but without uri parameter validations. So it
just dont care about the jms selector parameters you may set. They are
just skipped and not in use.
On Tue, Dec 17, 2013 at 9:12 PM, smadarapu <sr...@adp.com> wrote:
> Thanks Clause, one more question, i will still be able to consume from this
> endpoint, correct ?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p5744961.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
Re: Stubbing jms with an inprocess transport when using
CamelTestSupport
Posted by smadarapu <sr...@adp.com>.
Thanks Clause, one more question, i will still be able to consume from this
endpoint, correct ?
--
View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p5744961.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using CamelTestSupport
Posted by Claus Ibsen <cl...@gmail.com>.
You can use stub endpoint
http://camel.apache.org/stub
On Tue, Dec 17, 2013 at 8:48 PM, smadarapu <sr...@adp.com> wrote:
> I have the same issue, but the question here is if I can have jms selectors
> on a SEDA endpoint or not. Having different values based on the environment
> is secondary, i cant even configure the selectors with a SEDA endpoint. I
> must be missing something, forgive my ignorance.
>
> I see this exception as the OP
>
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> com.workscape.isi.camelrouting.InputFileCollectorRouteBuilder:INPUT_FILE_COLLECTOR_ROUTE_MQ1:TenantActive:
> Route(com.workscape.isi.camelrouting.InputFileCollectorRoute... because of
> Failed to resolve endpoint:
> jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27 due to: Failed to
> resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
> due to: There are 1 parameters that couldn't be set on the endpoint. Check
> the uri if the parameters are spelt correctly and that they are properties
> of the endpoint. Unknown parameters=[{selector=CustID = 'TenantActive'}]
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:182)
> at
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:770)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1914)
> at
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1670)
> at
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1544)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1512)
> at
> org.apache.camel.test.junit4.CamelTestSupport.startCamelContext(CamelTestSupport.java:476)
> at
> org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:310)
> at
> org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:216)
> at
> com.workscape.isi.camelrouting.InputFileCollectorRouteTest.setUp(InputFileCollectorRouteTest.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
> due to: Failed to resolve endpoint:
> jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27 due to: There are 1
> parameters that couldn't be set on the endpoint. Check the uri if the
> parameters are spelt correctly and that they are properties of the endpoint.
> Unknown parameters=[{selector=CustID = 'TenantActive'}]
> at
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:528)
> at
> org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:63)
> at
> org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:192)
> at
> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:106)
> at
> org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:112)
> at
> org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
> at
> org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:88)
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:890)
> at
> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:177)
> ... 36 more
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
> resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
> due to: There are 1 parameters that couldn't be set on the endpoint. Check
> the uri if the parameters are spelt correctly and that they are properties
> of the endpoint. Unknown parameters=[{selector=CustID = 'TenantActive'}]
> at
> org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:189)
> at
> org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:134)
> at
> org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:508)
> ... 44 more
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p5744959.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
Re: Stubbing jms with an inprocess transport when using
CamelTestSupport
Posted by smadarapu <sr...@adp.com>.
I have the same issue, but the question here is if I can have jms selectors
on a SEDA endpoint or not. Having different values based on the environment
is secondary, i cant even configure the selectors with a SEDA endpoint. I
must be missing something, forgive my ignorance.
I see this exception as the OP
org.apache.camel.FailedToCreateRouteException: Failed to create route
com.workscape.isi.camelrouting.InputFileCollectorRouteBuilder:INPUT_FILE_COLLECTOR_ROUTE_MQ1:TenantActive:
Route(com.workscape.isi.camelrouting.InputFileCollectorRoute... because of
Failed to resolve endpoint:
jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27 due to: Failed to
resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{selector=CustID = 'TenantActive'}]
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:182)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:770)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1914)
at
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1670)
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1544)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1512)
at
org.apache.camel.test.junit4.CamelTestSupport.startCamelContext(CamelTestSupport.java:476)
at
org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:310)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:216)
at
com.workscape.isi.camelrouting.InputFileCollectorRouteTest.setUp(InputFileCollectorRouteTest.java:136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
due to: Failed to resolve endpoint:
jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27 due to: There are 1
parameters that couldn't be set on the endpoint. Check the uri if the
parameters are spelt correctly and that they are properties of the endpoint.
Unknown parameters=[{selector=CustID = 'TenantActive'}]
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:528)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:63)
at
org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:192)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:106)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:112)
at
org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
at
org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:88)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:890)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:177)
... 36 more
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint: jms://queue1:msgs?selector=CustID+%3D+%27TenantActive%27
due to: There are 1 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{selector=CustID = 'TenantActive'}]
at
org.apache.camel.impl.DefaultComponent.validateParameters(DefaultComponent.java:189)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:134)
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:508)
... 44 more
--
View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p5744959.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using CamelTestSupport
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Aug 11, 2011 at 10:06 AM, jason.parr <ja...@usa.net> wrote:
> Thanks for the suggestion - externalising the endpoints urls in different
> property files for prod/test seemed the most sensible way to go.
>
Yeah this is common practice. This is also what we cover in chapter 6
in the Camel in Action book.
There is also the adviceWith feature in Camel that allows you to
manipulate routes before unit testing them.
http://camel.apache.org/advicewith.html
> --
> View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p4688766.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: Stubbing jms with an inprocess transport when using
CamelTestSupport
Posted by "jason.parr" <ja...@usa.net>.
Thanks for the suggestion - externalising the endpoints urls in different
property files for prod/test seemed the most sensible way to go.
--
View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p4688766.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using CamelTestSupport
Posted by Christian Müller <ch...@gmail.com>.
You can also externalize the endpoint configuration (the string) and use the
properties placeholder configurer. Than you can use different configurations
for different environments (dev, test, prod).
Sent from a mobile device
Am 10.08.2011 12:28 schrieb "jason.parr" <ja...@usa.net>:
> Hi,
>
> I want to test my 'production' route unchanged using CamelTestSupport.
>
> As show in the doco I stub out jms component with an inprocess trasnport
say
> seda:
>
> @Override
> protected CamelContext createCamelContext() throws Exception {
> CamelContext context = super.createCamelContext();
> context.addComponent("jms", context.getComponent("seda"));
> ...
>
> This works fine until any of my jms endpoints in the 'production' route
have
> jms specific parameter, e.g.
>
> from("direct:tradebus-trades")
> .to("jms:topic:NOMURA.FIET.STP.RADIAL.TRADES?&disableReplyTo=true");
>
> When I run my test I now get:
>
> org.apache.camel.FailedToCreateRouteException: ... There are 1 parameters
> that couldn't be set on the endpoint. Check the uri if the parameters are
> spelt correctly and that they are properties of the endpoint. Unknown
> parameters=[{disableReplyTo=true}]
>
> What's the best way of replacing jms with an inprocess transport without
> having to change the original route?
>
> In my test I add an extra a file endpoint to play messages into the
original
> route, which seems to work fine.
>
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RadialRouteBuilder() {
> @Override
> public void configure() {
> super.configure();
>
>
>
from("file:src/test/data/radial-route-builder-test-case?noop=true&include=bond_msg.*")
> .to("jms:queue:nomura.fiet.stp.bloomberg.bond-trades");
>
> Thanks
>
> --
> View this message in context:
http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p4685084.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Stubbing jms with an inprocess transport when using CamelTestSupport
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You can use the mock component instead. However you cannot consume
from a mock endpoint.
For JMS you can also easily embed and use Apache ActiveMQ.
On Wed, Aug 10, 2011 at 10:36 AM, jason.parr <ja...@usa.net> wrote:
> Hi,
>
> I want to test my 'production' route unchanged using CamelTestSupport.
>
> As show in the doco I stub out jms component with an inprocess trasnport say
> seda:
>
> @Override
> protected CamelContext createCamelContext() throws Exception {
> CamelContext context = super.createCamelContext();
> context.addComponent("jms", context.getComponent("seda"));
> ...
>
> This works fine until any of my jms endpoints in the 'production' route have
> jms specific parameter, e.g.
>
> from("direct:tradebus-trades")
> .to("jms:topic:NOMURA.FIET.STP.RADIAL.TRADES?&disableReplyTo=true");
>
> When I run my test I now get:
>
> org.apache.camel.FailedToCreateRouteException: ... There are 1 parameters
> that couldn't be set on the endpoint. Check the uri if the parameters are
> spelt correctly and that they are properties of the endpoint. Unknown
> parameters=[{disableReplyTo=true}]
>
> What's the best way of replacing jms with an inprocess transport without
> having to change the original route?
>
> In my test I add an extra a file endpoint to play messages into the original
> route, which seems to work fine.
>
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RadialRouteBuilder() {
> @Override
> public void configure() {
> super.configure();
>
>
> from("file:src/test/data/radial-route-builder-test-case?noop=true&include=bond_msg.*")
> .to("jms:queue:nomura.fiet.stp.bloomberg.bond-trades");
>
> Thanks
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Stubbing-jms-with-an-inprocess-transport-when-using-CamelTestSupport-tp4685084p4685084.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/