Re: DirectVmConsumerNotAvailableException cannot be caught by onException?

[bocamel]

Claus,

Thank you very much for the quick response which makes a lot of sense.  But
how can I mark the original exception (1st error) as "handled" to prevent
the exchange from being processed again and again.

Thanks,
John



--
View this message in context: 
http://camel.465427.n5.nabble.com/DirectVmConsumerNotAvailableException-cannot-be-caught-by-onException-tp5775185p5775189.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Create endpoints in java to use in xml routes

[mtkilbay]

Claus, thank you for responding. I think you know i meant EndpointRegistry.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Create-endpoints-in-java-to-use-in-xml-routes-tp5775092p5775190.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Easiest way to send a reply via camel-netty4:udp socket?

[SteveR]

- I have a Camel input route whereby camel-netty4 creates/binds a UDP socket
that listens on port 12345: 

*from("netty4:udp://host:12345? ...)
.to("SEDA_QUEUE1" ...);*

- The input route receives a UDP datagram, creates the exchange, and sends
it to *SEDA_QUEUE1*.

- Then the exchange from *SEDA_QUEUE1* is sent to some other queue (e.g.
*SEDA_QUEUE2*) which has a processor that formulates a UDP exchange message
that I want to send back as a reply message via the input route's UDP
socket.

This reply exchange has the *CamelNettyLocalAddress* and
*CamelNettyRemoteAddress *headers containing the associated local/remote IP
and port.

How, from a processor within the route consuming from *SEDA_QUEUE2*, do I
send the reply out the UDP socket on the input route?  There was to be an
easy way to do this, but I'm not seeing it.

  Thanks, SteveR


I've been trying with code similar to this within a processor on the
*SEDA_QUEUE2*, but no luck so far:

ProducerTemplate template = context.createProducerTemplate();
Endpoint endpoint = context.getEndpoint("netty4:udp ...");
Exchange replyExchange = endpoint.createExchange();
replyExchange.getIn().setBody("UDP REPLY MESSAGE");
replyExchange.getIn().setHeaders(exchange.getIn().getHeaders());
template.send(endpoint, replyExchange);












--
View this message in context: 
http://camel.465427.n5.nabble.com/Easiest-way-to-send-a-reply-via-camel-netty4-udp-socket-tp5775186.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [ENHANCEMENT REQUEST]: camel-netty4 config support for specifying UDP source port

[Claus Ibsen]

We love contributions, so you are much welcome to dive in the code to
see if that sourcePort can be added.
http://camel.apache.org/contributing


On Mon, Dec 14, 2015 at 11:36 PM, SteveR  wrote:
> I'm currently facing a show-stopping production issue: I'm unable to figure
> out how to specify the UDP source port of my choosing for a Camel route that
> uses the  camel-netty4    component to
> send a UDP datagram.
>
> If anyone has any thoughts/ideas about how I can do this (or hack this) it
> would be much appreciated.
>
> For details, see my recent Camel-Users post:  How to specify the UDP source
> port with camel-netty4 ?
> 
>
> It would be great if this could be taken under consideration for an upcoming
> enhancement.  It looks like the main changes would be in the associated
> NettyProducer.java
> 
> and possibly made configurable via an addition to the  camel-netty4
>    options.
>
> For example:
>
> .to("netty4:udp://remotehost:12345?*sourcePort=5*&
>   clientPipelineFactory=#MY_CLIENT_PIPELINE_FACTORY&
>
> sync=false=false=26214400=false");
>
> Thanks, SteveR
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/ENHANCEMENT-REQUEST-camel-netty4-config-support-for-specifying-UDP-source-port-tp5775070.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

DirectVmConsumerNotAvailableException cannot be caught by onException?

[bocamel]

I have the following context level OnException.  After it catches an error,
it would send out an email alert using a direct-vm route.  But to avoid
infinite loop, the email alert is only sent if the OnException is not
entered due to a nested exception.

When the direct-vm consumer is not started and there is an exception (e.g.
ValidationException), the OnException is entered and then fail with
org.apache.camel.component.directvm.DirectVmConsumerNotAvailableException
which is expected.  I had expected that the
DirectVmConsumerNotAvailableException is caught by the OnException again.
But it was not. I need to catch it so that the original ValidationException
can be "handled".  Any suggestion?


org.apache.camel.InvalidPayloadException
org.apache.camel.ValidationException
org.apache.camel.CamelException
org.apache.camel.CamelExchangeException

org.apache.camel.component.directvm.DirectVmConsumerNotAvailableException
java.lang.Exception
java.lang.RuntimeException
true

exchange.properties.eb_already_in_recovery !=
'true'
   
 
true











--
View this message in context: 
http://camel.465427.n5.nabble.com/DirectVmConsumerNotAvailableException-cannot-be-caught-by-onException-tp5775185.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Create endpoints in java to use in xml routes

[Claus Ibsen]

No that is not possible. There is a JIRA ticket to improve this in the
future. Its not an easy change.



On Wed, Dec 16, 2015 at 5:38 PM, mtkilbay  wrote:
> My question may not have been clear enough so let me ask a specific question:
>
> Does anyone know whether i can use the EndpointRepository to add an endpoint
> with a reference name, e.g., "kafkatopic" that i can then refer to in my xml
> route like below:
> 
>
> Thanks.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Create-endpoints-in-java-to-use-in-xml-routes-tp5775092p5775183.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: DirectVmConsumerNotAvailableException cannot be caught by onException?

[Claus Ibsen]

That is by design to not handle errors while handling errors, eg you
can easily get in endless looping. When that happens Camel detect it
and does a fatal fallback error handling where the 2nd error is
logged.


On Wed, Dec 16, 2015 at 6:08 PM, bocamel  wrote:
> I have the following context level OnException.  After it catches an error,
> it would send out an email alert using a direct-vm route.  But to avoid
> infinite loop, the email alert is only sent if the OnException is not
> entered due to a nested exception.
>
> When the direct-vm consumer is not started and there is an exception (e.g.
> ValidationException), the OnException is entered and then fail with
> org.apache.camel.component.directvm.DirectVmConsumerNotAvailableException
> which is expected.  I had expected that the
> DirectVmConsumerNotAvailableException is caught by the OnException again.
> But it was not. I need to catch it so that the original ValidationException
> can be "handled".  Any suggestion?
>
> 
> org.apache.camel.InvalidPayloadException
> org.apache.camel.ValidationException
> org.apache.camel.CamelException
> org.apache.camel.CamelExchangeException
>
> org.apache.camel.component.directvm.DirectVmConsumerNotAvailableException
> java.lang.Exception
> java.lang.RuntimeException
> true
> 
> exchange.properties.eb_already_in_recovery 
> !=
> 'true'
> 
> true
> 
> 
> 
> 
> 
> 
> 
> 
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/DirectVmConsumerNotAvailableException-cannot-be-caught-by-onException-tp5775185.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Having issues with Multicast to Aggregation ...

[jtoepfer]

Sorry for the long delay, I got pulled onto another problem and am just
getting back to this issue.

@Jakub,

  The problem I'm encountering is upon aggregation, the file aggregation
either times out or is stuck in a wait pattern until all multiplex routes
have completed.  I can see in the logs where several of the routes complete,
but a single route just hangs.  Trying to perform a shutdown of ActiveMQ I
get the message waiting for shutdown for 300 seconds.  I'm assuming the this
is due to my route waiting for a response.  

I ended up going the brute force method of calling all the SQL components in
one route, and a route to zip up the generated files.  I was hoping to take
advantage the power of camel, but wasn't in the cards for this time around. 
Another issue arose, was that upgrading camel versions in our environment
meant for more regression testing.  Something I couldn't get buy-in from the
users.



-
Josh Toepfer
--
View this message in context: 
http://camel.465427.n5.nabble.com/Having-issues-with-Multicast-to-Aggregation-tp5774688p5775194.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Add my own Filter on http4?

[burner]

Hello together,

i want to use a own headerFilterStrategy on my own Component extends from
http4.

So I create this class:
public class DefaultHeaderFilterStrategy extends HttpHeaderFilterStrategy {

public DefaultHeaderFilterStrategy() {
super();
getOutFilter().add("MessageHistory");
getInFilter().add("MessageHistory");
System.err.println(getOutFilter().toString());
// I get [date, content-length, transfer-encoding, upgrade, 
pragma, via,
trailer, *MessageHistory*, host, warning, content-type, connection,
cache-control]
}

public boolean applyFilterToCamelHeaders(String headerName, Object
headerValue, Exchange exchange) {
boolean test = super.applyFilterToCamelHeaders(headerName, 
headerValue,
exchange);
System.err.println("Camel return "+test+ " for "+headerName);
*// Here I get false for MessageHistory*
return test;
}

public boolean applyFilterToExternalHeaders(String headerName, Object
headerValue, Exchange exchange) {
boolean test = super.applyFilterToExternalHeaders(headerName,
headerValue, exchange);
System.err.println("Extern return "+test+ " for "+headerName);
*// Here I get false for MessageHistory*
return test;
}
}

and in my Component extends from
org.apache.camel.component.http4.HttpComponent I override the Method
createEndpoint and change the line:

From
if (headerFilterStrategy != null) {
endpoint.setHeaderFilterStrategy(headerFilterStrategy);
} else {
setEndpointHeaderFilterStrategy(endpoint);
}

To

if (headerFilterStrategy != null) {
endpoint.setHeaderFilterStrategy(headerFilterStrategy);
} else {
*   headerFilterStrategy = new 
DefaultHeaderFilterStrategy();
endpoint.setHeaderFilterStrategy(headerFilterStrategy);*
setEndpointHeaderFilterStrategy(endpoint);
}

It print out, that my Filter is in getOutFilter. But it always sends out in
the header from a http Post request.

Why? How can I filter out a Camel Header, without to remove the header vom
the Exchange?

Thank you for help.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Add-my-own-Filter-on-http4-tp5775147.html
Sent from the Camel - Users mailing list archive at Nabble.com.

ServiceFactory of Cxf Endpoint is not working

[Joseph Kampf]

I am trying to specify the ServiceFactory used by my CXF Endpoint.













However I am getting the following error:

karaf@root()> Exception in thread "SpringOsgiExtenderThread-50" 
org.apache.camel.RuntimeCamelException: 
org.apache.camel.FailedToCreateRouteException: Failed to create route 
aria.esbservices.complete.soap.proxy: 
Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
lookup: cxfBeanFromEndpoint from registry: 
org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with expected 
type: class org.apache.camel.component.cxf.CxfEndpoint due: Error creating bean 
with name 'cxfBeanFromEndpoint': Error setting property values; nested 
exception is org.springframework.beans.NotWritablePropertyException: Invalid 
property 'serviceFactory' of bean class 
[org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
'serviceFactory' is not writable or has an invalid setter method. Does the 
parameter type of the setter match the return type of the getter?
at 
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1363)
at 
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:122)
at 
org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:318)
at 
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
at 
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
at 
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:950)
at 
org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at 
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at 
org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at 
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at 
org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create 
route aria.esbservices.complete.soap.proxy: 
Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
lookup: cxfBeanFromEndpoint from registry: 
org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with expected 
type: class org.apache.camel.component.cxf.CxfEndpoint due: Error creating bean 
with name 'cxfBeanFromEndpoint': Error setting property values; nested 
exception is org.springframework.beans.NotWritablePropertyException: Invalid 
property 'serviceFactory' of bean class 
[org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
'serviceFactory' is not writable or has an invalid setter method. Does the 
parameter type of the setter match the return type of the getter?
at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:180)
at 
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:780)
at 
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:2068)
at 
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1816)
at 
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1683)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at 
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1651)
at 
org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:254)
at 
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:120)
... 10 more
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve 
endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot lookup: 
cxfBeanFromEndpoint from registry: 
org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with expected 
type: class org.apache.camel.component.cxf.CxfEndpoint due: Error creating bean 
with name 'cxfBeanFromEndpoint': Error setting property values; nested 
exception is org.springframework.beans.NotWritablePropertyException: Invalid 
property 'serviceFactory' of bean class 
[org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
'serviceFactory' is not writable or has an invalid setter method. Does the 
parameter type of the setter match the return type of the getter?
at 

Re: Add my own Filter on http4?

[burner]

I found the Error!

All cases must be lower!
so this work:
getOutFilter().add("messagehistory");

This don't work:
getOutFilter().add("MessageHistory");




--
View this message in context: 
http://camel.465427.n5.nabble.com/Add-my-own-Filter-on-http4-tp5775147p5775152.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: ServiceFactory of Cxf Endpoint is not working

[Claus Ibsen]

That was a mistake in the camel cxf documentation - i am removing
that. Also that other xml file is not in use in an unit test and its
being removed as well.

You dont need to set that service factory when using camel-cxf. Just
remove it from your code.



On Wed, Dec 16, 2015 at 1:21 PM, Joseph Kampf  wrote:
> I am trying to specify the ServiceFactory used by my CXF Endpoint.
>
>  address="${esbservices.proxy.baseurl}/path"
> serviceClass="MyPortClass"
> endpointName="s:completePort" serviceName="s:aria_complete_api"
> wsdlURL="MyWsdl.wsdl"
> xmlns:s="myNamespace">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> However I am getting the following error:
>
> karaf@root()> Exception in thread "SpringOsgiExtenderThread-50" 
> org.apache.camel.RuntimeCamelException: 
> org.apache.camel.FailedToCreateRouteException: Failed to create route 
> aria.esbservices.complete.soap.proxy: 
> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
> lookup: cxfBeanFromEndpoint from registry: 
> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with expected 
> type: class org.apache.camel.component.cxf.CxfEndpoint due: Error creating 
> bean with name 'cxfBeanFromEndpoint': Error setting property values; nested 
> exception is org.springframework.beans.NotWritablePropertyException: Invalid 
> property 'serviceFactory' of bean class 
> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
> 'serviceFactory' is not writable or has an invalid setter method. Does the 
> parameter type of the setter match the return type of the getter?
> at 
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1363)
> at 
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:122)
> at 
> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:318)
> at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
> at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
> at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:950)
> at 
> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
> at 
> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
> at 
> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at 
> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
> at 
> org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create 
> route aria.esbservices.complete.soap.proxy: 
> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
> lookup: cxfBeanFromEndpoint from registry: 
> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with expected 
> type: class org.apache.camel.component.cxf.CxfEndpoint due: Error creating 
> bean with name 'cxfBeanFromEndpoint': Error setting property values; nested 
> exception is org.springframework.beans.NotWritablePropertyException: Invalid 
> property 'serviceFactory' of bean class 
> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
> 'serviceFactory' is not writable or has an invalid setter method. Does the 
> parameter type of the setter match the return type of the getter?
> at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:180)
> at 
> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:780)
> at 
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:2068)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1816)
> at 
> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1683)
> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
> at 
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1651)
> at 
> org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:254)
> at 
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:120)
> ... 10 more
> Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve 
> endpoint: 

Re: ServiceFactory of Cxf Endpoint is not working

[Joseph Kampf]

So I am having an issue getting the right Service Factory.

Clearing out the karaf/data/cache directory and then doing a fresh deploy of 
the Bundle works fine.  

However after restarting Karaf the org.apache.cxf.jaxws.JaxWsServerFactoryBean 
is not used by the CxfEndpoint.  Instead the 
org.apache.cxf.frontend.ServerFactoryBean is used.  This causes the mapping of 
WSDL Operations to SEI methods to not work.

This results in error messages:


2015-12-15 09:51:18,729 | WARN  | xtenderThread-42 | 
ReflectionServiceFactoryBean | 194 - org.apache.cxf.cxf-rt-core - 2.7.11 | 
No method was found for the WSDL operation <%WSDL Operation%>


It also causes the CXF page to not list the WSDL Operations under the SOAP 
Port.  

The reason this is happening is because the annotations that are on the SEI 
class are proxied.  This causes the annotation check in 
org.apache.camel.component.cxf.CxfSpringEndpoint.createServerFactoryBean() to 
seem as if the SEI does not have the javax.jws.WebService annotation.  The 
annotation is on the list of annotations for the SEI, but they are proxied by 
sun.reflect.annotation.AnnotationInvocationHandler.



My work around (one I don’t like) is to:

* Remove the serviceClass attribute of the 
* Set the Data Format of the endpoint to: PAYLOAD
* Use a JaxBFormat to take the raw XML to the POJO.

The reason this work is that Camel is forcing the use of JaxWsServerFactoryBean 
when there is no SEI defined and the Dataformat is PAYLOAD.

Thanks,

Joe Kampf






On 12/16/15, 9:29 AM, "Claus Ibsen"  wrote:

>That was a mistake in the camel cxf documentation - i am removing
>that. Also that other xml file is not in use in an unit test and its
>being removed as well.
>
>You dont need to set that service factory when using camel-cxf. Just
>remove it from your code.
>
>
>
>On Wed, Dec 16, 2015 at 1:21 PM, Joseph Kampf  wrote:
>> I am trying to specify the ServiceFactory used by my CXF Endpoint.
>>
>> > address="${esbservices.proxy.baseurl}/path"
>> serviceClass="MyPortClass"
>> endpointName="s:completePort" serviceName="s:aria_complete_api"
>> wsdlURL="MyWsdl.wsdl"
>> xmlns:s="myNamespace">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> However I am getting the following error:
>>
>> karaf@root()> Exception in thread "SpringOsgiExtenderThread-50" 
>> org.apache.camel.RuntimeCamelException: 
>> org.apache.camel.FailedToCreateRouteException: Failed to create route 
>> aria.esbservices.complete.soap.proxy: 
>> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
>> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
>> lookup: cxfBeanFromEndpoint from registry: 
>> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with 
>> expected type: class org.apache.camel.component.cxf.CxfEndpoint due: Error 
>> creating bean with name 'cxfBeanFromEndpoint': Error setting property 
>> values; nested exception is 
>> org.springframework.beans.NotWritablePropertyException: Invalid property 
>> 'serviceFactory' of bean class 
>> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
>> 'serviceFactory' is not writable or has an invalid setter method. Does the 
>> parameter type of the setter match the return type of the getter?
>> at 
>> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1363)
>> at 
>> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:122)
>> at 
>> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:318)
>> at 
>> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:950)
>> at 
>> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
>> at 
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
>> at 
>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
>> at 
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
>> at 
>> org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create 
>> route aria.esbservices.complete.soap.proxy: 
>> 

Re: java dsl vs blueprint xml

[Matt Sicker]

How much cleaner is the Groovy DSL compared to using Java 8 with the Java
DSL?

On 16 December 2015 at 02:10, souciance 
wrote:

> I wouldn't mind using it but considering that most of the books and
> documentation is using the java or blueprint dsl so that makes it a bit
> easier.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775124.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Matt Sicker 

Re: Using Message Headers & Body into Camel SQL Insert statement

[Matt Sicker]

Headers are already interpolated like :#headerName. I've never tried using
expressions in SQL like that.

On 15 December 2015 at 13:44, Shiv  wrote:

> Hi,
> I want to insert a record in table using camel sql component and want to
> externalize the insert query in a properties file. Seems it is not working
> fine as simple expression in properties is not getting replaced by actual
> value.
>
> #Insert query in properties file - this is not working
> SQLInsertQuery=insert into Message (messageId, messageBody)
> values('$simple{in.header.JMSMessageID}', '$simple{in.body}')
>
> #Insert query in properties file - this is also not working
> SQLInsertQuery=insert into Message (messageId, messageBody)
> values('${in.header.JMSMessageID}', '${in.body}')
>
> #Insert query in properties file - this is also not working
> SQLInsertQuery=insert into Message (messageId, messageBody)
> values(:#${header.JMSMessageID}, :#${body}')
>
>
> My route calls below but insert is failing in call cases.
> 
>
> Am I missing anything in expression?
>
> Thanks for input.
> Shiv
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Using-Message-Headers-Body-into-Camel-SQL-Insert-statement-tp5775107.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Matt Sicker 

Re: ServiceFactory of Cxf Endpoint is not working

[Joseph Kampf]

BTW,

You should also consider removing the serviceFactory element from the XSD.  
That is also misleading.

Joe





On 12/16/15, 9:29 AM, "Claus Ibsen"  wrote:

>That was a mistake in the camel cxf documentation - i am removing
>that. Also that other xml file is not in use in an unit test and its
>being removed as well.
>
>You dont need to set that service factory when using camel-cxf. Just
>remove it from your code.
>
>
>
>On Wed, Dec 16, 2015 at 1:21 PM, Joseph Kampf  wrote:
>> I am trying to specify the ServiceFactory used by my CXF Endpoint.
>>
>> > address="${esbservices.proxy.baseurl}/path"
>> serviceClass="MyPortClass"
>> endpointName="s:completePort" serviceName="s:aria_complete_api"
>> wsdlURL="MyWsdl.wsdl"
>> xmlns:s="myNamespace">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>> However I am getting the following error:
>>
>> karaf@root()> Exception in thread "SpringOsgiExtenderThread-50" 
>> org.apache.camel.RuntimeCamelException: 
>> org.apache.camel.FailedToCreateRouteException: Failed to create route 
>> aria.esbservices.complete.soap.proxy: 
>> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
>> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
>> lookup: cxfBeanFromEndpoint from registry: 
>> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with 
>> expected type: class org.apache.camel.component.cxf.CxfEndpoint due: Error 
>> creating bean with name 'cxfBeanFromEndpoint': Error setting property 
>> values; nested exception is 
>> org.springframework.beans.NotWritablePropertyException: Invalid property 
>> 'serviceFactory' of bean class 
>> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
>> 'serviceFactory' is not writable or has an invalid setter method. Does the 
>> parameter type of the setter match the return type of the getter?
>> at 
>> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1363)
>> at 
>> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:122)
>> at 
>> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:318)
>> at 
>> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
>> at 
>> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:950)
>> at 
>> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
>> at 
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
>> at 
>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
>> at 
>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
>> at 
>> org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create 
>> route aria.esbservices.complete.soap.proxy: 
>> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
>> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
>> lookup: cxfBeanFromEndpoint from registry: 
>> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with 
>> expected type: class org.apache.camel.component.cxf.CxfEndpoint due: Error 
>> creating bean with name 'cxfBeanFromEndpoint': Error setting property 
>> values; nested exception is 
>> org.springframework.beans.NotWritablePropertyException: Invalid property 
>> 'serviceFactory' of bean class 
>> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
>> 'serviceFactory' is not writable or has an invalid setter method. Does the 
>> parameter type of the setter match the return type of the getter?
>> at org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:180)
>> at 
>> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:780)
>> at 
>> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:2068)
>> at 
>> org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1816)
>> at 
>> org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1683)
>> at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
>> at 
>> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1651)
>> at 
>> 

Re: ServiceFactory of Cxf Endpoint is not working

[Claus Ibsen]

Okay found a mistake in the cxf namespace parser - and added a fix for
correct setter on the endpoint.

Nobody really use that service factory as camel sets one out of the box.

On Wed, Dec 16, 2015 at 3:58 PM, Joseph Kampf  wrote:
> BTW,
>
> You should also consider removing the serviceFactory element from the XSD.  
> That is also misleading.
>
> Joe
>
>
>
>
>
> On 12/16/15, 9:29 AM, "Claus Ibsen"  wrote:
>
>>That was a mistake in the camel cxf documentation - i am removing
>>that. Also that other xml file is not in use in an unit test and its
>>being removed as well.
>>
>>You dont need to set that service factory when using camel-cxf. Just
>>remove it from your code.
>>
>>
>>
>>On Wed, Dec 16, 2015 at 1:21 PM, Joseph Kampf  wrote:
>>> I am trying to specify the ServiceFactory used by my CXF Endpoint.
>>>
>>> >> address="${esbservices.proxy.baseurl}/path"
>>> serviceClass="MyPortClass"
>>> endpointName="s:completePort" serviceName="s:aria_complete_api"
>>> wsdlURL="MyWsdl.wsdl"
>>> xmlns:s="myNamespace">
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>> However I am getting the following error:
>>>
>>> karaf@root()> Exception in thread "SpringOsgiExtenderThread-50" 
>>> org.apache.camel.RuntimeCamelException: 
>>> org.apache.camel.FailedToCreateRouteException: Failed to create route 
>>> aria.esbservices.complete.soap.proxy: 
>>> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
>>> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
>>> lookup: cxfBeanFromEndpoint from registry: 
>>> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with 
>>> expected type: class org.apache.camel.component.cxf.CxfEndpoint due: Error 
>>> creating bean with name 'cxfBeanFromEndpoint': Error setting property 
>>> values; nested exception is 
>>> org.springframework.beans.NotWritablePropertyException: Invalid property 
>>> 'serviceFactory' of bean class 
>>> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
>>> 'serviceFactory' is not writable or has an invalid setter method. Does the 
>>> parameter type of the setter match the return type of the getter?
>>> at 
>>> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1363)
>>> at 
>>> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:122)
>>> at 
>>> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:318)
>>> at 
>>> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
>>> at 
>>> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
>>> at 
>>> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:950)
>>> at 
>>> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
>>> at 
>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
>>> at 
>>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
>>> at 
>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
>>> at 
>>> org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.apache.camel.FailedToCreateRouteException: Failed to create 
>>> route aria.esbservices.complete.soap.proxy: 
>>> Route(aria.esbservices.complete.soap.proxy)[[From[cxf:bean:a... because of 
>>> Failed to resolve endpoint: cxf://bean:cxfBeanFromEndpoint due to: Cannot 
>>> lookup: cxfBeanFromEndpoint from registry: 
>>> org.apache.camel.spring.spi.ApplicationContextRegistry@51cb33dc with 
>>> expected type: class org.apache.camel.component.cxf.CxfEndpoint due: Error 
>>> creating bean with name 'cxfBeanFromEndpoint': Error setting property 
>>> values; nested exception is 
>>> org.springframework.beans.NotWritablePropertyException: Invalid property 
>>> 'serviceFactory' of bean class 
>>> [org.apache.camel.component.cxf.CxfSpringEndpoint]: Bean property 
>>> 'serviceFactory' is not writable or has an invalid setter method. Does the 
>>> parameter type of the setter match the return type of the getter?
>>> at 
>>> org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:180)
>>> at 
>>> org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:780)
>>> at 
>>> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:2068)
>>> at 

Re: Camel Stream caching unable to capture the entire stream

[calyan.bandi]

Hi,

I found the anwer to the problem in apache cxf forums. 

http://cxf.547215.n5.nabble.com/How-to-increase-the-max-size-of-a-REST-response-td563077.html

This is more of a issue in the CXF component than camel. But still for
referene, i am sharing this information. 

At the server side, we saw the below response headers for each of the
requests.

ID: 2
Response-Code: 200
Content-Type: application/json
Headers: {Content-Type=[application/json], Date=[Wed, 16 Dec 2015 11:21:34
GMT]}
Messages: Outbound Message (saved to tmp file):
Filename: C:\Users\Temp\cxf-tmp-309797\cos8635606649006238176tmp
(message truncated to 65536 bytes)

And from the client logs, whatever the payload that is received from the
server, we are seeing only the first chunk in the logs (calculated the
response payload size from the logs and it is 65536 bytes). This is only a
concern during logging and in my camel routes at the client side the entire
response is getting unmarshalled from JSON and things are working fine.  

Thanks,
Kalyan



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Stream-caching-unable-to-capture-the-entire-stream-tp5775055p5775145.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Error in JPA based idempotent repository

[Максим Козлов]

Hi community,

This current project use JPA based idempotent repository and have exception:

[Camel (camel-1) thread #0 -] WARN
org.apache.camel.component.file.FileConsumer - Consumer
Consumer[file://D:%5C1?idempotent=true=%23jpaStore]
failed polling endpoint:
Endpoint[file://D:%5C1?idempotent=true=%23jpaStore].
Will try again at next poll. Caused by:
[org.apache.openjpa.persistence.InvalidStateException - This broker is not
configured to use managed transactions.]


org.apache.openjpa.persistence.InvalidStateException: This broker is not
configured to use managed transactions.

   at
org.apache.openjpa.kernel.BrokerImpl.syncWithManagedTransaction(BrokerImpl.java:1569)

   at
org.apache.openjpa.kernel.DelegatingBroker.syncWithManagedTransaction(DelegatingBroker.java:948)

   at
org.apache.openjpa.persistence.EntityManagerImpl.joinTransaction(EntityManagerImpl.java:558)

   at
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository$2.doInTransaction(JpaMessageIdRepository.java:131)

   at
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository$2.doInTransaction(JpaMessageIdRepository.java:128)

   at
org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133)

   at
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository.contains(JpaMessageIdRepository.java:128)

   at
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository.contains(JpaMessageIdRepository.java:120)

   at
org.apache.camel.processor.idempotent.jpa.JpaMessageIdRepository.contains(JpaMessageIdRepository.java:47)

   at
org.apache.camel.component.file.GenericFileConsumer.isValidFile(GenericFileConsumer.java:544)

   at
org.apache.camel.component.file.FileConsumer.pollDirectory(FileConsumer.java:96)

   at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:119)

   at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:174)

   at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:101)

   at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

   at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

   at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

   at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

   at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

   at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

   at java.lang.Thread.run(Thread.java:745)


Code:

EntityManagerFactory emf =
Persistence.createEntityManagerFactory("idempotentDb");

JpaMessageIdRepository jpaStore = new JpaMessageIdRepository(emf,
"AlphaConsumer");

SimpleRegistry reg = new SimpleRegistry();

reg.put("jpaStore", jpaStore);

CamelContext context = new DefaultCamelContext(reg);


* *<*persistence **version=**"2.0" **xmlns=*
*"http://java.sun.com/xml/ns/persistence
"  **xmlns:**xsi**=*
*"http://www.w3.org/2001/XMLSchema-instance
"  *
*xsi:schemaLocation=**"http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd
"*
>
<*persistence-unit **name=**"idempotentDb" **transaction-type=*
*"RESOURCE_LOCAL"*>
<*class*>org.apache.camel.processor.idempotent.jpa.MessageProcessed

<*properties*>
<*property **name=**"openjpa.ConnectionURL" **value=*
*"jdbc:oracle:thin:@*"*/>
<*property **name=**"openjpa.ConnectionDriverName" **value=*
*"oracle.jdbc.driver.OracleDriver"*/>
<*property **name=**"openjpa.ConnectionUserName" **value=*
*"***"*/>
   <*property **name=**"openjpa.ConnectionPassword" **value=**"***"*
/>
<*property **name=**"openjpa.Log" **value=**"DefaultLevel=WARN,
Tool=INFO"*/>
<*property **name=**"openjpa.Multithreaded" **value=**"true"*/>




-- 
Best regards Max Kozlov aka dream-x

Re: Create endpoints in java to use in xml routes

[mtkilbay]

My question may not have been clear enough so let me ask a specific question:

Does anyone know whether i can use the EndpointRepository to add an endpoint
with a reference name, e.g., "kafkatopic" that i can then refer to in my xml
route like below:


Thanks.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Create-endpoints-in-java-to-use-in-xml-routes-tp5775092p5775183.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Apache Camel as ETL

[souciance]

In general I would say integration is usually event-based and hopefully
asynchronous. It makes everything much easier to handle.

In your case it is batch oriented and you need to take action afterwards.

I am sure it can be achieved in Camel and you'd probably have to write
several customised code. The question is, whether Camel is the right tool
for this or whether it is better to use something that is designed for ETL
usage. There is the ETL pattern stated here:
http://camel.apache.org/etl-example.html

You can also off course try https://nifi.apache.org/ and see if having
another tool helps. I would say if you plan to do a lot of ETL it is better
to have a specific tool for this.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Apache-Camel-as-ETL-tp5775073p5775126.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: java dsl vs blueprint xml

[souciance]

I wouldn't mind using it but considering that most of the books and
documentation is using the java or blueprint dsl so that makes it a bit
easier.



--
View this message in context: 
http://camel.465427.n5.nabble.com/java-dsl-vs-blueprint-xml-tp5775085p5775124.html
Sent from the Camel - Users mailing list archive at Nabble.com.

deadLetterHandleNewException(false) seems to not work as expected

[lchdev]

I am trying to use the option /deadLetterHandleNewException(false)/ in order
to have any new Exception occurring during the dead letter processing be
propagated back. Unfortunately, when doing so, it seems that the dead letter
channel propagates back the original exception as well, even if the
DeadLetterChannel succeeded. This is definitely not the behavior that I
expected.

This has been tested with Camel 2.15.3 and 2.16.1, both behave in the same
(unexpected) way. Am I misconfiguring or misusing something ? Or is it a bug
? Here is a simple route (Java DSL) that is sufficient to illustrate the
behavior:


Sending a message to this route will trigger an Exception that will be
propagated back to the producer, even if we can see in the logs that the
DeadLetterChannel has successfully *handled* the exception.




--
View this message in context: 
http://camel.465427.n5.nabble.com/deadLetterHandleNewException-false-seems-to-not-work-as-expected-tp5775138.html
Sent from the Camel - Users mailing list archive at Nabble.com.