How to use special character for file consumer endpoint
I need to consume the refund_2013123.txt23408+0630.txt inside the tmp directory. Exchange exc= consumerTemplate.receive( file:/tmp?fileName=refund_2013123.txt23408+0630.txt); Then it is not consuming the file. I hope it is due to + character. When it is removed (from file name also) it is working. How can we give such characters into the URI. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-use-special-character-for-file-consumer-endpoint-tp5765049.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: How to use special character for file consumer endpoint
Hi See about raw values here http://camel.apache.org/how-do-i-configure-endpoints.html On Tue, Mar 31, 2015 at 8:33 AM, abkrt tharang...@gmail.com wrote: I need to consume the refund_2013123.txt23408+0630.txt inside the tmp directory. Exchange exc= consumerTemplate.receive( file:/tmp?fileName=refund_2013123.txt23408+0630.txt); Then it is not consuming the file. I hope it is due to + character. When it is removed (from file name also) it is working. How can we give such characters into the URI. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-use-special-character-for-file-consumer-endpoint-tp5765049.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: How to use special character for file consumer endpoint
Thank you very much... -- View this message in context: http://camel.465427.n5.nabble.com/How-to-use-special-character-for-file-consumer-endpoint-tp5765049p5765052.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Idepotent repository update inside a camel Processr
Thanks Claus Ibsen, Glad to hear from you. Yes I have see the idempotentConsumer EIP behaviour and I am ok with it, but I needed to remove the added message keys for the batch (added from the idempotent consumer) from the Idempotent Repository whenever the DB batch update fails, this ensure that, I can reprocess those messages/records of the batch as part of reprocessing mechanism. So I am only going to remove the keys from idempotent repository inside a customer processor whenever db update fails, other wise I will be still using idempotent consumer EIP in the route. Is this approach fine? thanks, Rafi -- View this message in context: http://camel.465427.n5.nabble.com/Idepotent-repository-update-inside-a-camel-Processr-tp5764924p5765051.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Bindy running within a WAR
Thanks, I've created a PackageScanClassResolver for my project that works
with WAR files.
In the documentation http://camel.apache.org/pluggable-class-resolvers.html
it says I simply need to create a spring bean but when I tried the bean was
never referenced. I had a quick look in DefaultCamelContext and
SpringCamelContext but all I could see was a hard coded reference to the
DefaultPackageScanClassResolver. My Spring config looks like this:
@Bean
BeltPackageScanClassResolver beltResolver() {
BeltPackageScanClassResolver resolver = new
BeltPackageScanClassResolver();
return resolver;
}
Am I missing something?
--
View this message in context:
http://camel.465427.n5.nabble.com/Bindy-running-within-a-WAR-tp5765035p5765077.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Apache Camel decodes HTTP query params and httpclient fails with Invalid query exception
Hi I logged a ticket https://issues.apache.org/jira/browse/CAMEL-8578 On Mon, Mar 30, 2015 at 10:58 AM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Yeah sounds like a little bug. You are welcome to log a JIRA. http://camel.apache.org/contributing.html On Thu, Mar 26, 2015 at 3:56 PM, Liliana.Neagul liliana.iovanov...@gmail.com wrote: @Willem: Yes I tried to the parameter in Exchange.HTTP_QUERY header name. It has the same behavior. -- View this message in context: http://camel.465427.n5.nabble.com/Apache-Camel-decodes-HTTP-query-params-and-httpclient-fails-with-Invalid-query-exception-tp5764794p5764843.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Apache Camel and web services
It looks there are more than one version of CXF in your class patch, can you
double check it?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 30, 2015 at 7:16:36 PM, Willian Antunes
(willian.lima.antu...@gmail.com) wrote:
I am trying to understand how to integrate Apache Camel with any web
service that provides a WSDL.
I've studied a little about camel-spring-ws
and camel-cxf
packages. As I can see Spring Web
Services Component does not support the use of WSDL but CXF does, however
it only supports connections with JAX-WS services hosted in CXF.
If I receive a WSDL from a customer, could I use CXF? Or would I need to
create a custom component to use his methods?
As far as I can see the simplest way to implement it would be creating a
Process or a Bean to invokes the remote web service or to configure the CXF
before the task.
I've tried to implement a producer to set the CXF call to a remove web
service . My beans.xml:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:cxf=http://camel.apache.org/schema/cxf;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd;
id=osvEndpoint
address=http://10.193.1.90:8767/;
serviceClass=siemens_hiq8000.SiemensHiq8000PortType/
class=br.com.willianantunes.logger.DownloadLogger /
class=br.com.willianantunes.logger.MessageFromQueueLogger /
class=br.com.willianantunes.processor.OsvWebServiceProcessor /
My route:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
xmlns=http://camel.apache.org/schema/spring;
And my processor:
public class OsvWebServiceProcessor implements Processor{
@Override
public void process(Exchange exchange) throws Exception
{
Message inMessage = exchange.getIn();
// The method to be called
inMessage.setHeader(CxfConstants.OPERATION_NAME, getVersion);
// Parameters to be passed into the web service
List params = new ArrayList();
ResultCodeStructHolder resultCodeStructHolder = new
ResultCodeStructHolder();
VersionDataHolder versionDataHolder = new VersionDataHolder();
params.add(resultCodeStructHolder);
params.add(versionDataHolder);
inMessage.setBody(params);
}}
The method getVersion needs some parameters as followed:
public void getVersion(siemens_hiq8000.holders.ResultCodeStructHolder result,
siemens_hiq8000.holders.VersionDataHolder versionData) throws
java.rmi.RemoteException;
How can I pass them? These holders must be filled with the response of the
web service. When I run my project I get the following error:
[main] INFO org.apache.cxf.service.factory.ReflectionServiceFactoryBean
- Creating Service {http://siemens_hiq8000/}SiemensHiq8000PortType
from class siemens_hiq8000.SiemensHiq8000PortTypeException in thread
main java.lang.NoSuchMethodError:
org.apache.cxf.wsdl11.WSDLEndpointFactory.createEndpointInfo(Lorg/apache/cxf/service/model/ServiceInfo;Lorg/apache/cxf/service/model/BindingInfo;Ljava/util/List;)Lorg/apache/cxf/service/model/EndpointInfo;
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:287)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:144)
at
org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:91)
at
org.apache.camel.component.cxf.CxfSpringEndpoint.createClient(CxfSpringEndpoint.java:116)
at org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:76)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:2869)
at
org.apache.camel.impl.DefaultCamelContext.doAddService(DefaultCamelContext.java:1097)
at
org.apache.camel.impl.DefaultCamelContext.addService(DefaultCamelContext.java:1058)
at org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:405)
at
org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:123)
at org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:219)
at
Re: Bindy running within a WAR
That is for using spring xml, with camelContext.
On Tue, Mar 31, 2015 at 12:59 PM, Ted na...@pritchard.uk.net wrote:
Thanks, I've created a PackageScanClassResolver for my project that works
with WAR files.
In the documentation http://camel.apache.org/pluggable-class-resolvers.html
it says I simply need to create a spring bean but when I tried the bean was
never referenced. I had a quick look in DefaultCamelContext and
SpringCamelContext but all I could see was a hard coded reference to the
DefaultPackageScanClassResolver. My Spring config looks like this:
@Bean
BeltPackageScanClassResolver beltResolver() {
BeltPackageScanClassResolver resolver = new
BeltPackageScanClassResolver();
return resolver;
}
Am I missing something?
--
View this message in context:
http://camel.465427.n5.nabble.com/Bindy-running-within-a-WAR-tp5765035p5765077.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Apache Camel and web services
Jiang, this is not the case. I had posted my doubt in Stackoverflow and I
updated with the solution.
http://stackoverflow.com/questions/29276308/apache-camel-and-web-services
There are no examples portraying this situation in the Apache Camel project
website. It was difficult a little for a starter!
Regards.
On Tue, Mar 31, 2015 at 9:10 AM, Willem Jiang willem.ji...@gmail.com
wrote:
It looks there are more than one version of CXF in your class patch, can
you double check it?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 30, 2015 at 7:16:36 PM, Willian Antunes (
willian.lima.antu...@gmail.com) wrote:
I am trying to understand how to integrate Apache Camel with any web
service that provides a WSDL.
I've studied a little about camel-spring-ws
and camel-cxf
packages. As I can see Spring Web
Services Component does not support the use of WSDL but CXF does, however
it only supports connections with JAX-WS services hosted in CXF.
If I receive a WSDL from a customer, could I use CXF? Or would I need to
create a custom component to use his methods?
As far as I can see the simplest way to implement it would be creating a
Process or a Bean to invokes the remote web service or to configure the
CXF
before the task.
I've tried to implement a producer to set the CXF call to a remove web
service . My beans.xml:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:cxf=http://camel.apache.org/schema/cxf;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd;
id=osvEndpoint
address=http://10.193.1.90:8767/;
serviceClass=siemens_hiq8000.SiemensHiq8000PortType/
class=br.com.willianantunes.logger.DownloadLogger /
class=br.com.willianantunes.logger.MessageFromQueueLogger /
class=br.com.willianantunes.processor.OsvWebServiceProcessor /
My route:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
xmlns=http://camel.apache.org/schema/spring;
And my processor:
public class OsvWebServiceProcessor implements Processor{
@Override
public void process(Exchange exchange) throws Exception
{
Message inMessage = exchange.getIn();
// The method to be called
inMessage.setHeader(CxfConstants.OPERATION_NAME, getVersion);
// Parameters to be passed into the web service
List params = new ArrayList();
ResultCodeStructHolder resultCodeStructHolder = new
ResultCodeStructHolder();
VersionDataHolder versionDataHolder = new VersionDataHolder();
params.add(resultCodeStructHolder);
params.add(versionDataHolder);
inMessage.setBody(params);
}}
The method getVersion needs some parameters as followed:
public void getVersion(siemens_hiq8000.holders.ResultCodeStructHolder
result,
siemens_hiq8000.holders.VersionDataHolder versionData) throws
java.rmi.RemoteException;
How can I pass them? These holders must be filled with the response of
the
web service. When I run my project I get the following error:
[main] INFO org.apache.cxf.service.factory.ReflectionServiceFactoryBean
- Creating Service {http://siemens_hiq8000/}SiemensHiq8000PortType
from class siemens_hiq8000.SiemensHiq8000PortTypeException in thread
main java.lang.NoSuchMethodError:
org.apache.cxf.wsdl11.WSDLEndpointFactory.createEndpointInfo(Lorg/apache/cxf/service/model/ServiceInfo;Lorg/apache/cxf/service/model/BindingInfo;Ljava/util/List;)Lorg/apache/cxf/service/model/EndpointInfo;
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:287)
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:144)
at
org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:91)
at
org.apache.camel.component.cxf.CxfSpringEndpoint.createClient(CxfSpringEndpoint.java:116)
at
org.apache.camel.component.cxf.CxfProducer.doStart(CxfProducer.java:76)
at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
at
org.apache.camel.impl.DefaultCamelContext.startService(DefaultCamelContext.java:2869)
at
spring boot and camel
Hi I'm playing around with getting an existing camel 2.14.1 application integrated with spring boot 1.2.2 and am having a hard time working out how to do it. I want to use the features of spring boot such as externalised properties and an executable war file. The first problem I encountered was that spring boot uses spring 4.1.x and this was incompatible with camel 2.14.x tests so I upgraded to camel 2.15.0. Next problem is what to do with the BridgePropertyPlaceholderConfigurer I already had which allowed me to share properties between Spring and Camel? Spring boot has its own way of looking up properties which makes the property place holder stuff redundant. If I delete the BridgePropertyPlaceholderConfigurer then camel has no way of getting properties declared in the spring DSL. Now I see there is a spring boot and camel integration bit here http://camel.apache.org/spring-boot.html which looks like it can solve the properties issue. I've tried it and I get errors regarding multiple camel contexts. I assume it must be creating its own camel context in addition to reading my existing one I had already declared. How do I tell it not to create one and just take the one I already have? Does anyone have a better idea of solving this? I simply want the properties in spring boot to be accessible by camel and use my existing routes defined in spring DSL. Thanks in advance.
Re: Camels stop without warning
Just prior to posting my question, I changed some things with my DB connection pool, and the system has been running for more than a day. Which is 100% better than it has run (over the last month). Could this have been caused by a poorly configured (default) thread pool profile? In turn, hiding the real problem? -- View this message in context: http://camel.465427.n5.nabble.com/Camels-stop-without-warning-tp5765046p5765108.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Apache Camel and web services
Thanks for the information, it’s time to polish the CXF related example to help
user speed up with camel-cxf :)
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 31, 2015 at 8:35:35 PM, Willian Antunes
(willian.lima.antu...@gmail.com) wrote:
Jiang, this is not the case. I had posted my doubt in Stackoverflow and I
updated with the solution.
http://stackoverflow.com/questions/29276308/apache-camel-and-web-services
There are no examples portraying this situation in the Apache Camel project
website. It was difficult a little for a starter!
Regards.
On Tue, Mar 31, 2015 at 9:10 AM, Willem Jiang
wrote:
It looks there are more than one version of CXF in your class patch, can
you double check it?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On March 30, 2015 at 7:16:36 PM, Willian Antunes (
willian.lima.antu...@gmail.com) wrote:
I am trying to understand how to integrate Apache Camel with any web
service that provides a WSDL.
I've studied a little about camel-spring-ws
and camel-cxf
packages. As I can see Spring Web
Services Component does not support the use of WSDL but CXF does, however
it only supports connections with JAX-WS services hosted in CXF.
If I receive a WSDL from a customer, could I use CXF? Or would I need to
create a custom component to use his methods?
As far as I can see the simplest way to implement it would be creating a
Process or a Bean to invokes the remote web service or to configure the
CXF
before the task.
I've tried to implement a producer to set the CXF call to a remove web
service . My beans.xml:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:cxf=http://camel.apache.org/schema/cxf;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd;
id=osvEndpoint
address=http://10.193.1.90:8767/;
serviceClass=siemens_hiq8000.SiemensHiq8000PortType/
class=br.com.willianantunes.logger.DownloadLogger /
class=br.com.willianantunes.logger.MessageFromQueueLogger /
class=br.com.willianantunes.processor.OsvWebServiceProcessor /
My route:
xmlns=http://www.springframework.org/schema/beans;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd;
xmlns=http://camel.apache.org/schema/spring;
And my processor:
public class OsvWebServiceProcessor implements Processor{
@Override
public void process(Exchange exchange) throws Exception
{
Message inMessage = exchange.getIn();
// The method to be called
inMessage.setHeader(CxfConstants.OPERATION_NAME, getVersion);
// Parameters to be passed into the web service
List params = new ArrayList();
ResultCodeStructHolder resultCodeStructHolder = new
ResultCodeStructHolder();
VersionDataHolder versionDataHolder = new VersionDataHolder();
params.add(resultCodeStructHolder);
params.add(versionDataHolder);
inMessage.setBody(params);
}}
The method getVersion needs some parameters as followed:
public void getVersion(siemens_hiq8000.holders.ResultCodeStructHolder
result,
siemens_hiq8000.holders.VersionDataHolder versionData) throws
java.rmi.RemoteException;
How can I pass them? These holders must be filled with the response of
the
web service. When I run my project I get the following error:
[main] INFO org.apache.cxf.service.factory.ReflectionServiceFactoryBean
- Creating Service {http://siemens_hiq8000/}SiemensHiq8000PortType
from class siemens_hiq8000.SiemensHiq8000PortTypeException in thread
main java.lang.NoSuchMethodError:
org.apache.cxf.wsdl11.WSDLEndpointFactory.createEndpointInfo(Lorg/apache/cxf/service/model/ServiceInfo;Lorg/apache/cxf/service/model/BindingInfo;Ljava/util/List;)Lorg/apache/cxf/service/model/EndpointInfo;
at
org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:287)
at
Re: Camels stop without warning
Could you post your route definitions? On Tue, Mar 31, 2015 at 12:57 AM, davedave nab...@scattered.com.au wrote: I'm running Camel (2.14.1) on ServiceMix (5.4.0), and have 21 routes across two bundles, including 11 timer producing endpoints. After around 10 hours (~1000 timer messages) of running, camel grinds to a halt, and only restarting the bundles resolves the issue. I have placed .log processors between each point in the route, and all running routes seems to halt at the same time (at various points in the route), with just a few rouge exchanges making it a few more hops over the following minutes. No more timers are fired, and in flight exchanges finish their current process but never make it to the next step in the route. There is nothing telltale in the logs, even set to DEBUG, everything just seems to stop, and I just get checkpoint debugs in the servicemix.log from activemq, until I restart the bundles. Once the bundles get the stop instruction, they actually begin routing again, but they also begin shutting down. I haven't tried running TRACE yet, as those 1000 messages get split in to many more thousands, and there'd be hundreds of megs of logs every minute being produced. And with it failing between 8 and 12 hours, there's a 4 hour window where it would need to be watched closely. Connecting to the JMX port, I can't see and deadlocked threads. Any ideas on how best to best debug this? -- View this message in context: http://camel.465427.n5.nabble.com/Camels-stop-without-warning-tp5765046.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Bindy running within a WAR
Okay, thanks Claus. -- View this message in context: http://camel.465427.n5.nabble.com/Bindy-running-within-a-WAR-tp5765035p5765084.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camels stop without warning
These are just a couple, the first is an example of a producing route, the second it one of the processing routes. Thanks for looking! Mark Webb wrote Could you post your route definitions? -- View this message in context: http://camel.465427.n5.nabble.com/Camels-stop-without-warning-tp5765046p5765091.html Sent from the Camel - Users mailing list archive at Nabble.com.
camel - exception handling
Hi
Am trying to catch an exception and based on that continue the flow. Using
below code. But on xml validation I get following
cvc-complex-type.2.4.a: Invalid content was found starting with element
'camel:continued'. One of
'{http://camel.apache.org/schema/spring:exception,
http://camel.apache.org/schema/spring:onWhen, http://camel.apache.org/
schema/spring:handled, http://camel.apache.org/schema/spring:aop,
http://camel.apache.org/schema/spring:aggregate,
http://camel.apache.org/schema/spring:bean,
http://camel.apache.org/schema/spring:doCatch, http://
camel.apache.org/schema/spring:when,
http://camel.apache.org/schema/spring:choice,
http://camel.apache.org/schema/spring:otherwise,
http://camel.apache.org/schema/spring:convertBodyTo,
http://camel.apache.org/
schema/spring:delay,
http://camel.apache.org/schema/spring:dynamicRouter,
http://camel.apache.org/schema/spring:enrich,
http://camel.apache.org/schema/spring:filter,
http://camel.apache.org/schema/spring:doFinally,
http://camel.apache.org/schema/spring:idempotentConsumer,
http://camel.apache.org/schema/spring:inOnly,
http://camel.apache.org/schema/spring:inOut,
http://camel.apache.org/schema/spring:intercept, http://
camel.apache.org/schema/spring:interceptFrom,
http://camel.apache.org/schema/spring:interceptSendToEndpoint,
http://camel.apache.org/schema/spring:loadBalance,
http://camel.apache.org/schema/spring:log, http://
camel.apache.org/schema/spring:loop,
http://camel.apache.org/schema/spring:marshal,
http://camel.apache.org/schema/spring:multicast,
http://camel.apache.org/schema/spring:onCompletion,
http://camel.apache.org/
schema/spring:onException,
http://camel.apache.org/schema/spring:pipeline,
http://camel.apache.org/schema/spring:policy,
http://camel.apache.org/schema/spring:pollEnrich,
http://camel.apache.org/schema/
spring:process, http://camel.apache.org/schema/spring:recipientList,
http://camel.apache.org/schema/spring:removeHeader,
http://camel.apache.org/schema/spring:removeHeaders,
http://camel.apache.org/schema/
spring:removeProperties,
http://camel.apache.org/schema/spring:removeProperty,
http://camel.apache.org/schema/spring:resequence,
http://camel.apache.org/schema/spring:rollback,
http://camel.apache.org/schema/
spring:route, http://camel.apache.org/schema/spring:routingSlip,
http://camel.apache.org/schema/spring:sample,
http://camel.apache.org/schema/spring:setBody,
http://camel.apache.org/schema/spring:setExchangePattern,
http://camel.apache.org/schema/spring:setFaultBody,
http://camel.apache.org/schema/spring:setHeader,
http://camel.apache.org/schema/spring:setOutHeader,
http://camel.apache.org/schema/spring:setProperty, http://
camel.apache.org/schema/spring:sort,
http://camel.apache.org/schema/spring:split,
http://camel.apache.org/schema/spring:stop,
http://camel.apache.org/schema/spring:threads,
http://camel.apache.org/schema/
spring:throttle, http://camel.apache.org/schema/spring:throwException,
http://camel.apache.org/schema/spring:to,
http://camel.apache.org/schema/spring:transacted,
http://camel.apache.org/schema/spring:transform,
http://camel.apache.org/schema/spring:doTry,
http://camel.apache.org/schema/spring:unmarshal,
http://camel.apache.org/schema/spring:validate,
http://camel.apache.org/schema/spring:whenSkipSendToEndpoint, http://
camel.apache.org/schema/spring:wireTap,
http://camel.apache.org/schema/spring:restBinding}' is expected.
*doTry
camel:unmarshal
ref=xmljsonWithOptions /
doCatch
camel:exceptionnet.sf.json.JSONException/camel:exception
camel:continued
camel:constanttrue/camel:constant
/camel:continued
/doCatch
doFinally
camel:log
logName=Redknee-ib-NTTInterface
loggingLevel=INFO
message=Wrong
JSON String. Continuing the
flow still.. /
/doFinally
/doTry*
How can we fix this?
Cheers
Reji
-
Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel
Jboss Fuse ESB | Mule ESB )
LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
Twitter - reji_mathews
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-exception-handling-tp5765089.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel elasticsearch component
Any quick suggestions will be more helpful... -- View this message in context: http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765090.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel - exception handling
Continued is not a valid option in the catch block. By default the route will
continue since it is the assumption that the catch logic will handle any any
failures and continue. You can set the camel:handledfalse/camel:handled if
you want to propagate the exception.
- Andy
--
Andrew Block
M: (716) 870-2408
On March 31, 2015 at 5:39:27 PM, contactreji (contactr...@gmail.com) wrote:
Hi
Am trying to catch an exception and based on that continue the flow. Using
below code. But on xml validation I get following
cvc-complex-type.2.4.a: Invalid content was found starting with element
'camel:continued'. One of
'{http://camel.apache.org/schema/spring:exception,
http://camel.apache.org/schema/spring:onWhen, http://camel.apache.org/
schema/spring:handled, http://camel.apache.org/schema/spring:aop,
http://camel.apache.org/schema/spring:aggregate,
http://camel.apache.org/schema/spring:bean,
http://camel.apache.org/schema/spring:doCatch, http://
camel.apache.org/schema/spring:when,
http://camel.apache.org/schema/spring:choice,
http://camel.apache.org/schema/spring:otherwise,
http://camel.apache.org/schema/spring:convertBodyTo,
http://camel.apache.org/
schema/spring:delay,
http://camel.apache.org/schema/spring:dynamicRouter,
http://camel.apache.org/schema/spring:enrich,
http://camel.apache.org/schema/spring:filter,
http://camel.apache.org/schema/spring:doFinally,
http://camel.apache.org/schema/spring:idempotentConsumer,
http://camel.apache.org/schema/spring:inOnly,
http://camel.apache.org/schema/spring:inOut,
http://camel.apache.org/schema/spring:intercept, http://
camel.apache.org/schema/spring:interceptFrom,
http://camel.apache.org/schema/spring:interceptSendToEndpoint,
http://camel.apache.org/schema/spring:loadBalance,
http://camel.apache.org/schema/spring:log, http://
camel.apache.org/schema/spring:loop,
http://camel.apache.org/schema/spring:marshal,
http://camel.apache.org/schema/spring:multicast,
http://camel.apache.org/schema/spring:onCompletion,
http://camel.apache.org/
schema/spring:onException,
http://camel.apache.org/schema/spring:pipeline,
http://camel.apache.org/schema/spring:policy,
http://camel.apache.org/schema/spring:pollEnrich,
http://camel.apache.org/schema/
spring:process, http://camel.apache.org/schema/spring:recipientList,
http://camel.apache.org/schema/spring:removeHeader,
http://camel.apache.org/schema/spring:removeHeaders,
http://camel.apache.org/schema/
spring:removeProperties,
http://camel.apache.org/schema/spring:removeProperty,
http://camel.apache.org/schema/spring:resequence,
http://camel.apache.org/schema/spring:rollback,
http://camel.apache.org/schema/
spring:route, http://camel.apache.org/schema/spring:routingSlip,
http://camel.apache.org/schema/spring:sample,
http://camel.apache.org/schema/spring:setBody,
http://camel.apache.org/schema/spring:setExchangePattern,
http://camel.apache.org/schema/spring:setFaultBody,
http://camel.apache.org/schema/spring:setHeader,
http://camel.apache.org/schema/spring:setOutHeader,
http://camel.apache.org/schema/spring:setProperty, http://
camel.apache.org/schema/spring:sort,
http://camel.apache.org/schema/spring:split,
http://camel.apache.org/schema/spring:stop,
http://camel.apache.org/schema/spring:threads,
http://camel.apache.org/schema/
spring:throttle, http://camel.apache.org/schema/spring:throwException,
http://camel.apache.org/schema/spring:to,
http://camel.apache.org/schema/spring:transacted,
http://camel.apache.org/schema/spring:transform,
http://camel.apache.org/schema/spring:doTry,
http://camel.apache.org/schema/spring:unmarshal,
http://camel.apache.org/schema/spring:validate,
http://camel.apache.org/schema/spring:whenSkipSendToEndpoint, http://
camel.apache.org/schema/spring:wireTap,
http://camel.apache.org/schema/spring:restBinding}' is expected.
*doTry
camel:unmarshal ref=xmljsonWithOptions /
doCatch
camel:exceptionnet.sf.json.JSONException/camel:exception
camel:continued
camel:constanttrue/camel:constant
/camel:continued
/doCatch
doFinally
camel:log logName=Redknee-ib-NTTInterface
loggingLevel=INFO
message=Wrong
JSON String. Continuing the flow still.. /
/doFinally
/doTry*
How can we fix this?
Cheers
Reji
-
Reji Mathews
Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel
Jboss Fuse ESB | Mule ESB )
LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a
Twitter - reji_mathews
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-exception-handling-tp5765089.html
Sent from the Camel - Users mailing list archive at Nabble.com.
