Re: How to use PropertyPlaceholderConfigurer to configure the autoStartup option
Hi
See this page
http://camel.apache.org/using-propertyplaceholder.html
The syntax to use inside is {{ }}
On Sat, Jul 13, 2013 at 11:38 PM, bonnahu wrote:
> Hey guys,
> I am new to Camel. Currently, I want to use PropertyPlaceholderConfigurer to
> specify the autoStartup option in Camel route. Here is the
> PropertyPlaceholderConfigurer bean:
>
>
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
>
>
> autostartup.properties
>
>
>
>
>
>
> Here is the content of the autostartup.properties file:
>
> route.autostart=true
>
> Here is what I use in the spring DSL xml:
>
>
>
>
> The error I got is
>
> [OnException[[class... because of Error parsing [${route.autostart}] as a
> Boolean.
>
>
> Can anyone help me here?
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-use-PropertyPlaceholderConfigurer-to-configure-the-autoStartup-option-tp5735604.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
Re: How to use PropertyPlaceholderConfigurer to configure the autoStartup option
Hi
Which version of Camel are you using?
This issue is related to the schema definition, I think you need to disable the
Spring schema validation[1]
I just checked the latest camel spring schema, the attribute type of
autoStartup is string now, which means you will not hit this kind of issue in
latest released Camel.
[1]http://stackoverflow.com/questions/4160104/disable-schema-validation-in-spring-3
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Sunday, July 14, 2013 at 5:38 AM, bonnahu wrote:
> Hey guys,
> I am new to Camel. Currently, I want to use PropertyPlaceholderConfigurer to
> specify the autoStartup option in Camel route. Here is the
> PropertyPlaceholderConfigurer bean:
>
>
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>
>
>
> autostartup.properties
>
>
>
>
>
>
> Here is the content of the autostartup.properties file:
>
> route.autostart=true
>
> Here is what I use in the spring DSL xml:
>
>
>
>
> The error I got is
>
> [OnException[[class... because of Error parsing [${route.autostart}] as a
> Boolean.
>
>
> Can anyone help me here?
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/How-to-use-PropertyPlaceholderConfigurer-to-configure-the-autoStartup-option-tp5735604.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
>
Turning off warning message in ObjectHelper
While upgrading from camel 2.10.4 to camel 2.10.5, i noticed some additional warning messages in the ObjectHelper class, is there anyway to turn it off? The value is assigned correctly, just the annoying warning message. :( Below are the snippet of the configuration and logs. [DEBUG] o.s.b.f.s.DefaultListableBeanFactory> Returning cached instance of singleton bean 'testMap' [WARN ] o.a.c.u.ObjectHelper> Cannot find class: isMaster Thanks in advance. -- View this message in context: http://camel.465427.n5.nabble.com/Turning-off-warning-message-in-ObjectHelper-tp5735616.html Sent from the Camel - Users mailing list archive at Nabble.com.
Camel CXF WSDL first example
At long last I'm getting to spend time in Camel again. Writing a series of simple examples. Things folks I work with had trouble figuring out how to do mostly. Posted the first one athttp://code.notsoclever.cc/camel-cxf-component-wsdl-first-example/. tjs (slowly emerging from a year of PHP and C# hell)
Using GAuth to fetch all emails from a Gmail account
I've been reading the documentation about both the GAuth and IMAP components but I'm not clear on if what I'm trying is possible. I've also searched Google and the mailing list so I apologize if this has been asked before. I'm trying to figure out how to access all the messages in a Gmail account using OAuth 2.0. I don't need Camel to get the token, I already have a Rails frontend that deals with that. I tried seeing if the IMAP component can authenticate with OAuth but that doesn't seem possible though I'd be very happy if I'm wrong on that. Nor does the GAuth component appear to offer access to a user's entire message history, only new/unread messages using the Atom feed Google provides. Is what I'm looking for possible or do I need to find a different approach? Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/Using-GAuth-to-fetch-all-emails-from-a-Gmail-account-tp5735619.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: does hazelcast component support stand-alone HC server?
You can use the standard hazelcast XML configuration. There is no Camel specific magic. See http://www.hazelcast.com/ for a very detailed documentation. Best regards - Claus On 13.07.2013 13:21, Claus Ibsen wrote: I assume the idea is that you configure an existing com.hazelcast.core.HazelcastInstance on the HazelcastComponent which is then used. And the com.hazelcast.core.HazelcastInstance can refer to an external HC server. Though would be nice with some docs how to do that. On Sat, Jul 13, 2013 at 12:14 AM, 8forty <8fo...@gmail.com> wrote: It appears that it creates a local HC server on-the-fly, but I'd like to have it use my remote HC server. Is that possible? -- View this message in context: http://camel.465427.n5.nabble.com/does-hazelcast-component-support-stand-alone-HC-server-tp5735586.html Sent from the Camel - Users mailing list archive at Nabble.com.
DeadLetterErrorHandler queue not created
I configured a DeadLetterErrorHandler like that: and referenced it in my routes : the redeliveries work, but the DLQ is not created, or at least I can't see it anywhere. I check in activemq web console where i usually see all queues including ActiveMQ.DLQ, I tried activemq:queue:wecaDLQ and jms:queue:wecaDLQ but I can't see it anywhere. and the Messages Enqueued count and Messages Dequeued count on activemq web console increase by one. any idea? Thank you -- View this message in context: http://camel.465427.n5.nabble.com/DeadLetterErrorHandler-queue-not-created-tp5735624.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel CXF WSDL first example
Welcome back Tracy! And thanks for sharing your experience and solution. Feel free to link to your blog from our articles page [1]. I hope we will see more of this blogs in the future ;-) One note to this blog post. In the beginning, you write: 2. Create a Producer (our server) 3. Create a Consumer (client) that also acts as the test I think you mixed this up. Also because your consumer configuration is in camel-server-context.xml and your producer configuration is in camel-client-context.xml (which is right). [1] http://camel.apache.org/articles.html Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Sun, Jul 14, 2013 at 3:51 PM, Tracy Snell wrote: > At long last I'm getting to spend time in Camel again. Writing a series of > simple examples. Things folks I work with had trouble figuring out how to > do mostly. Posted the first one athttp:// > code.notsoclever.cc/camel-cxf-component-wsdl-first-example/. > > tjs (slowly emerging from a year of PHP and C# hell) > >
Re: DeadLetterErrorHandler queue not created
The queues are created lazy (when the first message is enqueued), but I
think the issue is:
You configured:
You should have configured:
Or is it a copy / past / modify issue?
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Sun, Jul 14, 2013 at 10:32 PM, shin938 wrote:
> I configured a DeadLetterErrorHandler like that:
>
> class="org.apache.camel.builder.DeadLetterChannelBuilder">
> value="activemq:queue:wecaDLQ"/>
> ref="wecaRedeliveryPolicyConfig"/>
>
>
>
> class="org.apache.camel.processor.RedeliveryPolicy">
> value="${weca.camel.redeliveryAttempts}"/>
>
>
>
>
> and referenced it in my routes :
>trace="${camel.context.trace}"
> depends-on="activemq,officeBundleActivator"
> errorHandlerRef="DeadLetterErrorHandler">
>
>
>
> the redeliveries work,
> but the DLQ is not created, or at least I can't see it anywhere. I check in
> activemq web console where i usually see all queues including ActiveMQ.DLQ,
> I tried activemq:queue:wecaDLQ and jms:queue:wecaDLQ
> but I can't see it anywhere.
> and the Messages Enqueued count and Messages Dequeued count on activemq
> web
> console increase by one.
> any idea?
>
> Thank you
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DeadLetterErrorHandler-queue-not-created-tp5735624.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: Error in camel-bindy
What issue do you hit? You should define the dependency to 2.9.x in your pom and exclude duplicated dependencies to 2.8.x. Executing mvn dependency:tree is helpful. Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Fri, Jul 12, 2013 at 10:30 PM, Jothi wrote: > After a bit of fiddling with it, I had to give up on the bindy component as > it does not fit to what I have. My domain model consist of a parent class > and a sub class where some of the fields are annotated in the parent class. > But this leads to an error when used with the bindy component. So this does > not fit my needs. Had to give up on the bindy component. > > Regards, > Joe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Error-in-camel-bindy-tp5735580p5735584.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: OneToMany in camel-bindy
Hi Joe! As you know, we love contributions. But I'm not sure whether I understood your proposed solution (I'm quite sure I understood your requirement). At present, the splitter EAI pattern + a content based router and multiple Bindy models could solve your requirement. Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Sat, Jul 13, 2013 at 8:06 AM, Jothi wrote: > Guys, > > Is this OneToMany a true OneToMany? I guess it only applies when the entire > CSV file has some common elements? I have a file that has entries like > below: > > 1,abc,def,joe > 1,abc,xyz,san > 2,abc,mno,ram > 3,abc,fgh,sam > > When I tried with the above file which used the OneToMany annotation > between > the Id and the rest of the fields, it threw an error saying that pos 2 must > be defined. I later took a look into the Camel documentation for bindy and > realized that the id's should all be the same throught the CSV file. > > Can we model the OneToMany in such a way that it takes a parameter for the > position and uses this to identify which field will be the One side? > Something like: > > OneToMany(pos=1) > > Is it reasonable enough to raise a Jira and provide a fix. I would be happy > to provide a fix. > > Regards, > Joe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/OneToMany-in-camel-bindy-tp5735591.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: CSV files processing
Bindy always maps an "ObjectMaster" and the contained objects to one line
[1].
[1]
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-bindy/src/main/java/org/apache/camel/dataformat/bindy/csv/BindyCsvDataFormat.java;h=3ab36149f803b665eac43e42bbde09bada86d329;hb=HEAD
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Jul 12, 2013 at 2:43 PM, Jothi wrote:
> I have a Bindy bean written as below:
>
> public class ObjectMaster {
>
> private String field1;
>
> @OneToMany
> private List < Object1 > field2;
>
> @OneToMany
> private List < Object2 > field3;
> }
>
> I have two CSV files in which unmarshalling one of them would produce a one
> to many relationship with ObjectMaster and Object1 and the other CSV file
> will produce the one to many relationship with ObjectMaster and Object2. Is
> this possible with the camel bindy?
>
> Regards,
> Joe
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/CSV-files-processing-tp5735470p5735570.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: JMS route transaction timeout
OnException should come before transacted [1]. [1] http://camel.465427.n5.nabble.com/transacted-in-combination-with-onException-td5719591.html Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Wed, Jul 10, 2013 at 5:18 PM, swwyatt wrote: > Hi, > > I am having an issue with configuring a JMS route with onException. With a > route defined similar to that below, when an exception occurs, the message > is properly sent to myDLQ. But, when there is a transaction timeout due to > the longRunningProcessor taking too long, the message cannot be sent to > myDLQ (due to rollback) and the message is rollback to myQueue and > redelivered. > > I can add an additional route under a new transaction in order to commit > the > message to myDLQ, but the message still is rolled back and redelivered. > > Is the a way to handle the transaction timeout in the same manner as > onException? I just basically want to move the message to myDLQ for any > exception including transaction timeout. > > v2.8.1 > > > > > > > java.lang.Exception > > true > > > > > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/JMS-route-transaction-timeout-tp5735455.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: REST best practices
There is no component which supports this specific requirement. You have to write your own bean which parse the returned HTML and find the HTTP URI's. Afterwards you can use the producer template [1] to access this URI's. [1] http://camel.apache.org/producertemplate.html Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Fri, Jul 12, 2013 at 11:02 PM, humayun0156 wrote: > i'm new in camel. i want to design a camel application which sync two > servers. > server1: > this server send a message to camel application. this message has a HTTP > link which we should download and this downloaded message has another > multiple HTTP link which we should download by HTTP GET request and so on. > Now we aggregate all the downloaded things and send it to server2 HTTP post > request and from the response of post request we should modify some of > server1 resource by PUT request. > > so my question is which component should i use in this scenario which > support dynamically picked HTTP uri? > > Thanks in advance. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/REST-best-practices-tp5735585.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
Re: Get the exception org.apache.camel.RuntimeCamelException: java.lang.RuntimeException: Protocol mismatch for port 443: engine's protocol is http, the url protocol is https
> Now I modified the CamelCXFProviderRouteConfig.xml in the same project.
What did you modify?
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Jul 12, 2013 at 11:18 AM, cannykanna wrote:
> Hi
> I am using the camel-cxf example and created a project in eclipse.
> In src/main/java
> org.apache.camel.example.Provider package, I created my own Client which
> talks to end application.
> I used this client in my CamelCxfExample.java Class and modified the tester
> bean as well.
> Now I modified the CamelCXFProviderRouteConfig.xml in the same project.
>
> Now when I run mvn exec:java -PWebServiceProvider command from eclipse, I
> am getting below stack of error:
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Camel :: Example :: CXF 2.11.0
> [INFO]
>
> [INFO]
> [INFO] >>> exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> >>>
> [INFO]
> [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (versions) @
> camel-example-cxf ---
> [INFO]
> [INFO] <<< exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> <<<
> [INFO]
> [INFO] --- exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> ---
> [rovider.CamelCxfExample.main()] ClassPathXmlApplicationContext INFO
> Refreshing
> org.springframework.context.support.ClassPathXmlApplicationContext@6b5b5783
> :
> startup date [Fri Jul 12 12:35:44 IST 2013]; root of context hierarchy
> [rovider.CamelCxfExample.main()] XmlBeanDefinitionReaderINFO
> Loading XML bean definitions from class path resource
> [META-INF/spring/CamelCXFProviderRouteConfig.xml]
> [rovider.CamelCxfExample.main()] XmlBeanDefinitionReaderINFO
> Loading XML bean definitions from class path resource
> [META-INF/cxf/cxf.xml]
> [rovider.CamelCxfExample.main()] ClassPathXmlApplicationContext INFO Bean
> 'cxf' of type [class org.apache.cxf.bus.spring.SpringBus] is not eligible
> for getting processed by all BeanPostProcessors (for example: not eligible
> for auto-proxying)
> [rovider.CamelCxfExample.main()] DefaultListableBeanFactory INFO
> Pre-instantiating singletons in
>
> org.springframework.beans.factory.support.DefaultListableBeanFactory@3da997a
> :
> defining beans
>
> [bridgePropertyPlaceholder,cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,testBean,soapMessageEndpoint,template,consumerTemplate,test_context:beanPostProcessor,test_context];
> root of factory hierarchy
> [rovider.CamelCxfExample.main()] CamelContextFactoryBeanINFO
> Bridging Camel and Spring property placeholder configurer with id:
> bridgePropertyPlaceholder
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO
> Apache
> Camel 2.11.0 (CamelContext: test_context) is starting
> [rovider.CamelCxfExample.main()] ManagementStrategyFactory INFO JMX
> enabled.
> [rovider.CamelCxfExample.main()] DefaultTypeConverter INFO
> Loaded
> 196 type converters
> [rovider.CamelCxfExample.main()] ReflectionServiceFactoryBean INFO
> Creating Service {http://www.service-now.com/incident}ServiceNow_incident
> from WSDL: wsdl/incident.do.wsdl
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO
> Apache
> Camel 2.11.0 (CamelContext: test_context) is shutting down
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO
> Uptime
> 0.898 seconds
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO
> Apache
> Camel 2.11.0 (CamelContext: test_context) is shutdown in 0.004 seconds
> Get the exception org.apache.camel.RuntimeCamelException:
> java.lang.RuntimeException: Protocol mismatch for port 443: engine's
> protocol is http, the url protocol is https
>
> My endpoint application runs on https protocol.
>
> Can you please help me.?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Get-the-exception-org-apache-camel-RuntimeCamelException-java-lang-RuntimeException-Protocol-mismatcs-tp5735568.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: org.apache.camel.CamelException: Cannot connect to
Will have a look in the coming week...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.org/foundation/members.html
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Wed, Jul 10, 2013 at 10:35 AM, kiranreddykasa wrote:
> Hi ,
>
> while performing load testing on the following route I am getting these
> error for *some *messages
>
> from("netty:tcp://0.0.0.0:7000?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7001?textline=true").to("netty:tcp://
> 0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7002?textline=true").to("netty:tcp://
> 0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7003?textline=true").to("netty:tcp://
> 0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class);
>
>
>
> Here is the full stacktrace
>
> ERROR 10 Jul 2013 12:32:35,252
> org.apache.camel.processor.DefaultErrorHandler - Failed delivery for
> (MessageId: ID-FSSCHN61-59989-1373476603039-0-73530 on ExchangeId:
> ID-FSSCHN61-59989-1373476603039-0-61620). Exhausted after delivery attempt:
> 1 caught: org.apache.camel.CamelException: Cannot connect to 0.0.0.0:7001
> org.apache.camel.CamelException: Cannot connect to 0.0.0.0:7001
> at
>
> org.apache.camel.component.netty.NettyProducer.openChannel(NettyProducer.java:404)
> at
>
> org.apache.camel.component.netty.NettyProducer$NettyProducerPoolableObjectFactory.makeObject(NettyProducer.java:472)
> at
>
> org.apache.camel.component.netty.NettyProducer$NettyProducerPoolableObjectFactory.makeObject(NettyProducer.java:467)
> at
>
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at
>
> org.apache.camel.component.netty.NettyProducer.process(NettyProducer.java:215)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
>
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:122)
> at
>
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:298)
> at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:117)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
>
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:335)
> at
>
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220)
> at
>
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
> org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:308)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
> at
>
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
> org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150)
> at
>
> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117)
> at
>
> org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
>
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
>
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
>
Re: org.apache.camel.CamelException: Cannot connect to
When you using 0.0.0.0:7000 on the server side, netty will listen to all the
net work interfaces, such as localhost and ips which you can access outside.
But 0.0.0.0 don't work for the client side, because we don't know which address
it really means, it could localhost or the other network interface.
You'd better change the address to localhost just like this
from("netty:tcp://0.0.0.0:7000?textline=true")
.bean(MainDummyProcessor.class)
.to("netty:tcp://0.0.0.0:7001?textline=true").to("netty:tcp://localhost:7004?textline=true")
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, July 10, 2013 at 4:35 PM, kiranreddykasa wrote:
> Hi ,
>
> while performing load testing on the following route I am getting these
> error for *some *messages
>
> from("netty:tcp://0.0.0.0:7000?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7001?textline=true").to("netty:tcp://0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7002?textline=true").to("netty:tcp://0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class)
> .to("netty:tcp://0.0.0.0:7003?textline=true").to("netty:tcp://0.0.0.0:7004?textline=true")
> .bean(MainDummyProcessor.class);
>
>
>
> Here is the full stacktrace
>
> ERROR 10 Jul 2013 12:32:35,252
> org.apache.camel.processor.DefaultErrorHandler - Failed delivery for
> (MessageId: ID-FSSCHN61-59989-1373476603039-0-73530 on ExchangeId:
> ID-FSSCHN61-59989-1373476603039-0-61620). Exhausted after delivery attempt:
> 1 caught: org.apache.camel.CamelException: Cannot connect to 0.0.0.0:7001
> org.apache.camel.CamelException: Cannot connect to 0.0.0.0:7001
> at
> org.apache.camel.component.netty.NettyProducer.openChannel(NettyProducer.java:404)
> at
> org.apache.camel.component.netty.NettyProducer$NettyProducerPoolableObjectFactory.makeObject(NettyProducer.java:472)
> at
> org.apache.camel.component.netty.NettyProducer$NettyProducerPoolableObjectFactory.makeObject(NettyProducer.java:467)
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
> at
> org.apache.camel.component.netty.NettyProducer.process(NettyProducer.java:215)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:122)
> at
> org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:298)
> at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:117)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:335)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:220)
> at
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:308)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
> at
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.UnitOfWorkProcessor.processAsync(UnitOfWorkProcessor.java:150)
> at
> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:117)
> at
> org.apache.camel.processor.RouteInflightRepositoryProcessor.processNext(RouteInflightRepositoryProcessor.java:48)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.a
Re: REST best practices
Hi, I imagine your implementation may be able to leverage the enrich enricher[0] pattern after receiving the initial request - or make use of recipientsList with in/out MEP and an expression language of your choice to extract out the required URL if it's dynamic - as suggested by your last line; Then you can use the splitter[1] pattern to xpath out all of the required links. On the splitter component you will provide an aggregator, which will aggregate all of the required downloads together. Then you can perform a simple `to` for the following notification to the second server. Hopefully this will help you out. Let me know if I misunderstood your use case :) Cheers, Alan [0] http://camel.apache.org/content-enricher.html [1] http://camel.apache.org/splitter.html -- View this message in context: http://camel.465427.n5.nabble.com/REST-best-practices-tp5735585p5735634.html Sent from the Camel - Users mailing list archive at Nabble.com.
Cannot access CamelLoopIndex in route using spel
I need to access CamelLoopIndex within a route. According to
http://camel.apache.org/loop.html, CamelLoopIndex is a property in the
Exchange while in the loop. I tried this simple test route:
Count
5
#{body + ':' +
property(CamelLoopIndex)}
But I received the error below. Any help will be greatly appreciated.
org.apache.camel.ExpressionEvaluationException:
org.springframework.expression.spel.SpelEvaluationException: EL1008E:(pos
22): Field or property 'CamelLoopIndex' cannot be found on object of type
'org.apache.camel.language.spel.RootObject'
at
org.apache.camel.language.spel.SpelExpression.evaluate(SpelExpression.java:64)
at
org.apache.camel.processor.SetBodyProcessor.process(SetBodyProcessor.java:38)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:390)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:273)
at
org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:335)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:103)
at
org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:74)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:390)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:273)
at
org.apache.camel.processor.RouteContextProcessor.processNext(Rout
Re: Get the exception org.apache.camel.RuntimeCamelException: java.lang.RuntimeException: Protocol mismatch for port 443: engine's protocol is http, the url protocol is https
Hi,
If you changed the protocol form http to https, you need to add some
configuration on the Jetty engine just like this[1]
[1]http://cxf.apache.org/docs/jetty-configuration.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Friday, July 12, 2013 at 5:18 PM, cannykanna wrote:
> Hi
> I am using the camel-cxf example and created a project in eclipse.
> In src/main/java
> org.apache.camel.example.Provider package, I created my own Client which
> talks to end application.
> I used this client in my CamelCxfExample.java Class and modified the tester
> bean as well.
> Now I modified the CamelCXFProviderRouteConfig.xml in the same project.
>
> Now when I run mvn exec:java -PWebServiceProvider command from eclipse, I
> am getting below stack of error:
> [INFO] Scanning for projects...
> [INFO]
> [INFO]
>
> [INFO] Building Camel :: Example :: CXF 2.11.0
> [INFO]
>
> [INFO]
> [INFO] >>> exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> > >
> >
>
>
> [INFO]
> [INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (versions) @
> camel-example-cxf ---
> [INFO]
> [INFO] <<< exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> <<<
> [INFO]
> [INFO] --- exec-maven-plugin:1.1.1:java (default-cli) @ camel-example-cxf
> ---
> [rovider.CamelCxfExample.main()] ClassPathXmlApplicationContext INFO
> Refreshing
> org.springframework.context.support.ClassPathXmlApplicationContext@6b5b5783:
> startup date [Fri Jul 12 12:35:44 IST 2013]; root of context hierarchy
> [rovider.CamelCxfExample.main()] XmlBeanDefinitionReader INFO
> Loading XML bean definitions from class path resource
> [META-INF/spring/CamelCXFProviderRouteConfig.xml]
> [rovider.CamelCxfExample.main()] XmlBeanDefinitionReader INFO
> Loading XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
> [rovider.CamelCxfExample.main()] ClassPathXmlApplicationContext INFO Bean
> 'cxf' of type [class org.apache.cxf.bus.spring.SpringBus] is not eligible
> for getting processed by all BeanPostProcessors (for example: not eligible
> for auto-proxying)
> [rovider.CamelCxfExample.main()] DefaultListableBeanFactory INFO
> Pre-instantiating singletons in
> org.springframework.beans.factory.support.DefaultListableBeanFactory@3da997a:
> defining beans
> [bridgePropertyPlaceholder,cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProcessor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,testBean,soapMessageEndpoint,template,consumerTemplate,test_context:beanPostProcessor,test_context];
> root of factory hierarchy
> [rovider.CamelCxfExample.main()] CamelContextFactoryBean INFO
> Bridging Camel and Spring property placeholder configurer with id:
> bridgePropertyPlaceholder
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO Apache
> Camel 2.11.0 (CamelContext: test_context) is starting
> [rovider.CamelCxfExample.main()] ManagementStrategyFactory INFO JMX
> enabled.
> [rovider.CamelCxfExample.main()] DefaultTypeConverter INFO Loaded
> 196 type converters
> [rovider.CamelCxfExample.main()] ReflectionServiceFactoryBean INFO
> Creating Service {http://www.service-now.com/incident}ServiceNow_incident
> from WSDL: wsdl/incident.do.wsdl
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO Apache
> Camel 2.11.0 (CamelContext: test_context) is shutting down
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO Uptime
> 0.898 seconds
> [rovider.CamelCxfExample.main()] SpringCamelContext INFO Apache
> Camel 2.11.0 (CamelContext: test_context) is shutdown in 0.004 seconds
> Get the exception org.apache.camel.RuntimeCamelException:
> java.lang.RuntimeException: Protocol mismatch for port 443: engine's
> protocol is http, the url protocol is https
>
> My endpoint application runs on https protocol.
>
> Can you please help me.?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Get-the-exception-org-apache-camel-RuntimeCamelException-java-lang-RuntimeException-Protocol-mismatcs-tp5735568.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
Re: Cannot access CamelLoopIndex in route using spel
Hi,
If you want to access the CamelLoopIndex, you should use
properties['CamelLoopIndex'] instead of property(CamelLoopIndex).
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Monday, July 15, 2013 at 9:24 AM, bocamel wrote:
> I need to access CamelLoopIndex within a route. According to
> http://camel.apache.org/loop.html, CamelLoopIndex is a property in the
> Exchange while in the loop. I tried this simple test route:
>
>
>
> Count
>
> 5
> #{body + ':' +
> property(CamelLoopIndex)}
>
>
>
>
> But I received the error below. Any help will be greatly appreciated.
>
>
> org.apache.camel.ExpressionEvaluationException:
> org.springframework.expression.spel.SpelEvaluationException: EL1008E:(pos
> 22): Field or property 'CamelLoopIndex' cannot be found on object of type
> 'org.apache.camel.language.spel.RootObject'
> at
> org.apache.camel.language.spel.SpelExpression.evaluate(SpelExpression.java:64)
> at
> org.apache.camel.processor.SetBodyProcessor.process(SetBodyProcessor.java:38)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:390)
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:273)
> at
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:335)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:103)
> at org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:74)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.jav
RE: Cannot access CamelLoopIndex in route using spel
Thanks Willem. Your suggestion worked beautifully.
From: Willem.Jiang [via Camel]
[mailto:ml-node+s465427n5735642...@n5.nabble.com]
Sent: Sunday, July 14, 2013 10:19 PM
To: bocamel
Subject: Re: Cannot access CamelLoopIndex in route using spel
Hi,
If you want to access the CamelLoopIndex, you should use
properties['CamelLoopIndex'] instead of property(CamelLoopIndex).
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Monday, July 15, 2013 at 9:24 AM, bocamel wrote:
> I need to access CamelLoopIndex within a route. According to
> http://camel.apache.org/loop.html, CamelLoopIndex is a property in the
> Exchange while in the loop. I tried this simple test route:
>
>
>
> Count
>
> 5
> #{body + ':' +
> property(CamelLoopIndex)}
>
>
>
>
> But I received the error below. Any help will be greatly appreciated.
>
>
> org.apache.camel.ExpressionEvaluationException:
> org.springframework.expression.spel.SpelEvaluationException: EL1008E:(pos
> 22): Field or property 'CamelLoopIndex' cannot be found on object of type
> 'org.apache.camel.language.spel.RootObject'
> at
> org.apache.camel.language.spel.SpelExpression.evaluate(SpelExpression.java:64)
>
> at
> org.apache.camel.processor.SetBodyProcessor.process(SetBodyProcessor.java:38)
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:91)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:390)
>
> at
> org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:273)
>
> at
> org.apache.camel.processor.RouteContextProcessor.processNext(RouteContextProcessor.java:46)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.processor.interceptor.DefaultChannel.process(DefaultChannel.java:335)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:117)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:80)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:103)
> at org.apache.camel.processor.LoopProcessor.process(LoopProcessor.java:74)
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:72)
>
> at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:73)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:99)
>
> at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:90)
>
> at
> org.apache.camel.processor.interceptor.BacklogTracerInterceptor.process(BacklogTracerInterceptor.java:84)
>
> at
> org.apac
Re: Accessing a local declared hashmap variable in a route
you can use camel-simple to do this...
from("direct:start")
.choice()
.when().simple("${body.keySet} contains 'foo'")
.to("mock:king")
.otherwise()
.to("mock:other");
clipod wrote
> Hi,
> I have a camel route with a choice block. I want to use a hashmap inside a
> when condition.
> To be more precise I would like to know if there is a way to use the
> "containsKey" function inside when.
> Is there a way to handle this. I can actually create a processor and
> define the behaviour but I would like to do it in the route itself.
-
Ben O'Day
IT Consultant -http://consulting-notes.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Accessing-a-local-declared-hashmap-variable-in-a-route-tp5735553p5735646.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: org.apache.camel.CamelException: Cannot connect to
Hi, As mentioned earlier only some of the requests (1%) are failing with the above exception, remaining all are processing successfully. - Regards kiran Reddy -- View this message in context: http://camel.465427.n5.nabble.com/org-apache-camel-CamelException-Cannot-connect-to-tp5735414p5735647.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Graceful shutdown not working
Tested, it works :) -- View this message in context: http://camel.465427.n5.nabble.com/Graceful-shutdown-not-working-tp5733697p5735648.html Sent from the Camel - Users mailing list archive at Nabble.com.
