Hi,
I am trying to rethrow an excepcion in a doTrydoCatch.
When I have this code:
bean id=forced class=java.lang.IllegalArgumentException
constructor-arg index=0 value=This is forced /
/bean
camelContext id=camel-route
xmlns=http://camel.apache.org/schema/spring;
route
Please have a look into the unit tests for the camel-spring-ws component
where we do this already.
Best,
Christian
Sent from a mobile device
Am 18.05.2012 01:45 schrieb ben_rr bin.k...@gmail.com:
Hi Christian
It is a bit hard to create a unit test because to recreate the problem
involves a
So
Christian Mueller wrote
It depends on your runtime environment, which Registry is used:
- org.apache.camel.spring.spi.ApplicationContextRegistry
- org.apache.camel.blueprint.BlueprintContainerRegistry
- org.apache.camel.impl.CompositeRegistry
- org.apache.camel.impl.JndiRegistry
-
I have a question concerning optional endpoints.
Background is that I want to do something like this:
from(anyActiveMQ-Queue)
.bean(anyProcessingBean)
.to(anotherActiveMQ-Queue)
*.to(additionalFileArchiveFolder)*; // optional
if the message should really go to the *additionalFileArchiveFolder
O.K. now I see the problem which is somehow similar to the one once I had as
well... However I went for another solution which was to simply list all my
persistence units in *one single* persistence.xml file. Then put this file
on your classpath which would make it accessible under the path
Patrick,
take a look at Message Filter EIP, you can configure the filter clause
based on properties loaded using camel:simple language.
att.
*Henrique Viecili*
On Fri, May 18, 2012 at 7:14 AM, prueegg patrick.ruee...@raiffeisen.chwrote:
I have a question concerning optional endpoints.
Hi Henrique
Thanks for your reply.
In the meantime I've found out, that an interceptor could do the job as
well.
The filter statement would allow me to switch on/off on the fly, where the
interceptor would be more static.
So I assume the filter and property solution would be the better one and
Hi Kai
Welcome back to Europe.
I had a quick look. I can see you figured out the __name__ naming of
the source files to allow the plugin to use dynamic names.
Well I guess you just copied the java version :)
It looks really good. Just a few thoughts.
I wonder if the scope of the log4j logging
Is it possible to relate to properties in the camel context as well?
All the examples I've seen are based on the properties of the exchange.
--
View this message in context:
http://camel.465427.n5.nabble.com/Optional-Endpoints-tp5711824p5711916.html
Sent from the Camel - Users mailing list
I have defined properties bean of type camel PropertiesComponent as shown
below. my.properties has
threadPool.defaultSize and threadPool.maxPoolSize properties defined.
However camel threadPoolProfile isn't able to recognize those properties and
keep complaining as follow.
Any idea?
bean
The documentation for intercepting routes at
http://camel.apache.org/advicewith.html shows using getRouteDefinition()
and adviceWith(). Both methods are deprecated now. Is there newer
documentation for this?
Thanks, Tom
Yes, if you use Spring DSL you can check it out at [1]
[1] http://camel.apache.org/using-propertyplaceholder.html
att.
*Henrique Viecili
*
On Fri, May 18, 2012 at 10:42 AM, prueegg patrick.ruee...@raiffeisen.chwrote:
Is it possible to relate to properties in the camel context as well?
All
Hi All,
I am looking to set up some mock test using Apache camel and I see
contradictory behaviours.
Please advice.
I am not sure if the mock is doing what is should (Verify if the headers are
set properly).
route
from uri=direct:dataToParse/
log message=Received xml from MocB ${body}/
choice
13 matches
Mail list logo
