Re: Camel without Spring. Limitations?
Camel and CXF support Blueprint which can do the same thing as Spring does. Did you have a chance to try it? 发自我的 iPhone 在 2013-6-3,下午6:59,Jose jagavi...@gmail.com 写道: Hi, I am trying to use Camel without Spring and I am wondering if there are some limitations. I guess the configuration would be more complicated but I wonder if I will loose some features. In particular, I am planning to use Camel with CXF. All the examples that I have seen use Camel with Spring. Thanks a lot. Jose -- View this message in context: http://camel.465427.n5.nabble.com/Camel-without-Spring-Limitations-tp5733686.html Sent from the Camel - Users mailing list archive at Nabble.com.
Transaction Management in Camel
HI, My route like this from(jms:queue:firstqueue) .transacted() .processor(new MyProcessor()) .to(jms:queue:out) --- in Myprocessor calss i am creating exchange message, and creating some dealy like thread.sleep() at the time of Thread sleeping i am stopping the server. Then again i started the jboss, the process is not continuing i lost that message, it is not available in persistace. i lost the exchange message. Can any one help on this one. Thanks in advance -- View this message in context: http://camel.465427.n5.nabble.com/Transaction-Management-in-Camel-tp5733762.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Graceful shutdown not working
I've tested with versions 2.10.3 and 2.11.0. This is just a short example that can reproduce described problem. You can put anything else in the splitter, it will not be reached. Reducing unnecessary code showed that example worked if seda was replaced with direct or maximumRedeliveries removed, so I guess problem is somehow related to that. Here is stack trace after it got stucked (I've paused the thread): Daemon Thread [Camel (camel-1) thread #0 - seda://queue1] (Suspended) DefaultCamelContext.getErrorHandlerExecutorService() line: 1321 DeadLetterChannel(RedeliveryErrorHandler).doStart() line: 1131 DeadLetterChannel(ChildServiceSupport).start(boolean) line: 41 DeadLetterChannel(ChildServiceSupport).start() line: 28 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 RouteContextProcessor(DelegateAsyncProcessor).doStart() line: 78 RouteContextProcessor(ServiceSupport).start() line: 61 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 UnitOfWorkProcessor(DelegateAsyncProcessor).doStart() line: 78 UnitOfWorkProcessor.doStart() line: 88 UnitOfWorkProcessor(ServiceSupport).start() line: 61 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 Splitter(MulticastProcessor).createErrorHandler(RouteContext, Exchange, Processor) line: 876 Splitter(MulticastProcessor).createProcessorExchangePair(int, Processor, Exchange, RouteContext) line: 833 Splitter$1$1.next() line: 178 Splitter$1$1.next() line: 133 Splitter.createProcessorExchangePairsList(Exchange, Object) line: 195 Splitter.createProcessorExchangePairs(Exchange) line: 113 Splitter(MulticastProcessor).process(Exchange, AsyncCallback) line: 206 Splitter.process(Exchange, AsyncCallback) line: 98 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 BacklogTracerInterceptor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 BacklogTracerInterceptor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 BacklogTracerInterceptor.process(Exchange, AsyncCallback) line: 84 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 TraceInterceptor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 TraceInterceptor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 TraceInterceptor.process(Exchange, AsyncCallback) line: 163 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 DeadLetterChannel(RedeliveryErrorHandler).processErrorHandler(Exchange, AsyncCallback, RedeliveryErrorHandler$RedeliveryData) line: 390 DeadLetterChannel(RedeliveryErrorHandler).process(Exchange, AsyncCallback) line: 273 RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 46 RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 DefaultChannel.process(Exchange, AsyncCallback) line: 335 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 Pipeline.process(Exchange, Exchange, AsyncCallback, IteratorProcessor, AsyncProcessor) line: 117 Pipeline.process(Exchange, AsyncCallback) line: 80 RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 46 RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 UnitOfWorkProcessor.processAsync(Exchange, AsyncCallback, UnitOfWork) line: 150 UnitOfWorkProcessor.process(Exchange, AsyncCallback) line: 117 RouteInflightRepositoryProcessor.processNext(Exchange, AsyncCallback) line: 48 RouteInflightRepositoryProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 InstrumentationProcessor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 InstrumentationProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 InstrumentationProcessor.process(Exchange, AsyncCallback) line: 72 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 SedaConsumer.sendToConsumers(Exchange) line: 275 SedaConsumer.doRun() line: 183 SedaConsumer.run() line: 139
Re: Graceful shutdown not working
Hi Thanks for reporting and providing the thread dumps. I logged a ticket and have a potential fix in the works. Would be great if you could test the fix in your system https://issues.apache.org/jira/browse/CAMEL-6421 On Tue, Jun 4, 2013 at 8:52 AM, miljenko miljenko.br...@2e-systems.com wrote: I've tested with versions 2.10.3 and 2.11.0. This is just a short example that can reproduce described problem. You can put anything else in the splitter, it will not be reached. Reducing unnecessary code showed that example worked if seda was replaced with direct or maximumRedeliveries removed, so I guess problem is somehow related to that. Here is stack trace after it got stucked (I've paused the thread): Daemon Thread [Camel (camel-1) thread #0 - seda://queue1] (Suspended) DefaultCamelContext.getErrorHandlerExecutorService() line: 1321 DeadLetterChannel(RedeliveryErrorHandler).doStart() line: 1131 DeadLetterChannel(ChildServiceSupport).start(boolean) line: 41 DeadLetterChannel(ChildServiceSupport).start() line: 28 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 RouteContextProcessor(DelegateAsyncProcessor).doStart() line: 78 RouteContextProcessor(ServiceSupport).start() line: 61 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 UnitOfWorkProcessor(DelegateAsyncProcessor).doStart() line: 78 UnitOfWorkProcessor.doStart() line: 88 UnitOfWorkProcessor(ServiceSupport).start() line: 61 ServiceHelper.startService(Service) line: 64 ServiceHelper.startService(Object) line: 54 ServiceHelper.startServices(Object...) line: 75 Splitter(MulticastProcessor).createErrorHandler(RouteContext, Exchange, Processor) line: 876 Splitter(MulticastProcessor).createProcessorExchangePair(int, Processor, Exchange, RouteContext) line: 833 Splitter$1$1.next() line: 178 Splitter$1$1.next() line: 133 Splitter.createProcessorExchangePairsList(Exchange, Object) line: 195 Splitter.createProcessorExchangePairs(Exchange) line: 113 Splitter(MulticastProcessor).process(Exchange, AsyncCallback) line: 206 Splitter.process(Exchange, AsyncCallback) line: 98 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 BacklogTracerInterceptor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 BacklogTracerInterceptor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 BacklogTracerInterceptor.process(Exchange, AsyncCallback) line: 84 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 TraceInterceptor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 TraceInterceptor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 TraceInterceptor.process(Exchange, AsyncCallback) line: 163 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 DeadLetterChannel(RedeliveryErrorHandler).processErrorHandler(Exchange, AsyncCallback, RedeliveryErrorHandler$RedeliveryData) line: 390 DeadLetterChannel(RedeliveryErrorHandler).process(Exchange, AsyncCallback) line: 273 RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 46 RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 DefaultChannel.process(Exchange, AsyncCallback) line: 335 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 Pipeline.process(Exchange, Exchange, AsyncCallback, IteratorProcessor, AsyncProcessor) line: 117 Pipeline.process(Exchange, AsyncCallback) line: 80 RouteContextProcessor.processNext(Exchange, AsyncCallback) line: 46 RouteContextProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 UnitOfWorkProcessor.processAsync(Exchange, AsyncCallback, UnitOfWork) line: 150 UnitOfWorkProcessor.process(Exchange, AsyncCallback) line: 117 RouteInflightRepositoryProcessor.processNext(Exchange, AsyncCallback) line: 48 RouteInflightRepositoryProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 AsyncProcessorHelper.process(AsyncProcessor, Exchange, AsyncCallback) line: 73 InstrumentationProcessor(DelegateAsyncProcessor).processNext(Exchange, AsyncCallback) line: 99 InstrumentationProcessor(DelegateAsyncProcessor).process(Exchange, AsyncCallback) line: 90 InstrumentationProcessor.process(Exchange, AsyncCallback) line: 72
Re: No bean named 'CamelBeanParameterMappingStrategy' is defined
If you don't use APM, can your camel context be started rightly? It looks like you are missing the definition of CamelBeanParameterMappingStrategy somewhere. -- 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 Tuesday, June 4, 2013 at 6:14 AM, salemi wrote: Hi, I started profilng my code with an APM software and I seeorg.springframework.beans.factory.NoSuchBeanDefinitionException and the message detail is No bean named 'CamelBeanParameterMappingStrategy' is defined. Did I miss something in my Spring Context? Thanks, Ali - Alireza Salemi -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-named-CamelBeanParameterMappingStrategy-is-defined-tp5733753.html Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF producer using Payload dataformat
Hi, Please don't send the same question into two different users mailing list. I already answer you question in the cxf users mailing list. The answer is you the response should be wrapped with soap envelope. -- 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 Tuesday, June 4, 2013 at 4:05 AM, Monga, Sunita (GE Healthcare) wrote: Hello all, I have a route which sends a request to CXF webservice using Payload dataformat. My question should the response consist of only Soap:body or should it be the entire message soap:envelope Spring context cxf:cxfEndpoint id=xdrReceiverEndpoint address=${xdrWebserviceUrl} endpointName=s:CcdaXdrServicePort serviceName=s:CcdaXdrService xmlns:s=http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com; cxf:properties entry key=mtom-enabled value=true/ entry key=dataFormat value=PAYLOAD/ entry key=loggingFeatureEnabled value=true/ !-- entry key=defaultOperationName value=submitCcda/-- /cxf:properties /cxf:cxfEndpoint Sample request: static final String REQ_MESSAGE=ccdaRequest xmlns=\ +http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService\; +clinicalDocument +ccDocument +xop:Include xmlns:xop=\http://www.w3.org/2004/08/xop/include\; + href=\cid: + REQ_DOC_CID + \/ +/ccDocument +/clinicalDocument +/ccdaRequest; I am trying to use SoapUI mockservice to mock the response as below ccdaResponse xmlns=http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService; !--Optional:-- ccdaAcknowledgement !--Optional:-- statusCode0/statusCode !--Optional:-- statusDescSuccess/statusDesc /ccdaAcknowledgement /ccdaResponse But I get following error [http-bio-8080-exec-1] WARN org.apache.cxf.phase.PhaseInterceptorChain - Interceptor for {http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com}CcdaXdrService#{http://camel.apache.org/cxf/jaxws/dispatch}Invoke has thrown exception, unwinding now org.apache.cxf.binding.soap.SoapFault: http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService;, the namespace on the ccdaResponse element, is not a valid SOAP version. at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:116) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:142) at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:61) If the response is the entire soap envelope I get following error. So not sure what the response should like org.apache.cxf.interceptor.Fault: Unexpected element {http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/CcdaXdrService}ccdaResponse found. Expected {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse. at org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLiteralInInterceptor.java:258) at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:200)
Re: the namespace on the IReportServiceExecuteRequest element, is not a valid SOAP version
Where did you call the exchange.getOut() ? -- 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 Tuesday, June 4, 2013 at 2:00 AM, sunita wrote: Hello, I am facing same issue. I get the same error - namespace is not a valid SOAP version. I added exchange.hasOut() before calling exchange.getOut(). hasOut returned true but getOut returned null headers and body Were you able to resolve the issue. -- View this message in context: http://camel.465427.n5.nabble.com/the-namespace-on-the-IReportServiceExecuteRequest-element-is-not-a-valid-SOAP-version-tp5284067p5733738.html Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: How to build a nested content based router?
See this FAQ about the endChoice https://camel.apache.org/why-can-i-not-use-when-or-otherwise-in-a-java-camel-route.html On Mon, Jun 3, 2013 at 4:05 PM, Hilde hilde.sch...@yahoo.de wrote: Hello Everybody, How can I model a nested content based router via the java dsl? The following trial was not successful: .choice() .when(header(CxfConstants.OPERATION_NAME).isEqualTo(importOrder)) .beanRef(logOrderConverter) .to(jpa:com.company.production.entities.OrderMerging) .choice() .when(method(routeCheck, checkSnapshot)) //content based router .to(activemq:queue: + JmsDestinations.QUEUE_ORDER_INPUT + ?disableReplyTo=true) .to(direct:endRoute) .otherwise() .process(new OrderConverter()) .to(activemq:queue: + JmsDestinations.QUEUE_DI_JOB + ?disableReplyTo=true) .to(direct:endRoute) .endChoice() .when(header(CxfConstants.OPERATION_NAME).isEqualTo(deleteBrandData)) .beanRef(convertWSBeanToOrderMergingEntityBean) .to(jpa:com.copany.production.entities.OrderMerging) .process(new OutMessageProcessor()) .endChoice(); Actually I don't know the differences between end() vs. endChoice(). Do you have any idea? Thanks in advanced! Cheers Hilde -- View this message in context: http://camel.465427.n5.nabble.com/How-to-build-a-nested-content-based-router-tp5733708.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: How to build a nested content based router?
You can use another route for the 2nd choice, and call that route using direct. That is easier and you make the routes smaller and easier to manage / test / understand etc. Just like java code with many if .. else nested is not a good idea. On Mon, Jun 3, 2013 at 4:05 PM, Hilde hilde.sch...@yahoo.de wrote: Hello Everybody, How can I model a nested content based router via the java dsl? The following trial was not successful: .choice() .when(header(CxfConstants.OPERATION_NAME).isEqualTo(importOrder)) .beanRef(logOrderConverter) .to(jpa:com.company.production.entities.OrderMerging) .choice() .when(method(routeCheck, checkSnapshot)) //content based router .to(activemq:queue: + JmsDestinations.QUEUE_ORDER_INPUT + ?disableReplyTo=true) .to(direct:endRoute) .otherwise() .process(new OrderConverter()) .to(activemq:queue: + JmsDestinations.QUEUE_DI_JOB + ?disableReplyTo=true) .to(direct:endRoute) .endChoice() .when(header(CxfConstants.OPERATION_NAME).isEqualTo(deleteBrandData)) .beanRef(convertWSBeanToOrderMergingEntityBean) .to(jpa:com.copany.production.entities.OrderMerging) .process(new OutMessageProcessor()) .endChoice(); Actually I don't know the differences between end() vs. endChoice(). Do you have any idea? Thanks in advanced! Cheers Hilde -- View this message in context: http://camel.465427.n5.nabble.com/How-to-build-a-nested-content-based-router-tp5733708.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Kryo Data format
Hello all, I was playing with the Kryo (https://code.google.com/p/kryo/) serialization library, comparing it to Java default serialization and Marshalling/Unmarshalling with JaxB. Taking aside Java Serialization, which would require me to implement Serializable and I can't, I like the fact that Kryo: - has serialized my JaxB Annotated classes 5 time faster than JaxB Marshalling - it has proved to be compatible using only the default FieldSerializer, which don't require to implement Serializable on the classes. I wonder if anyone has experience with Camel and Kryo and if anyone has ever thought of a camel-kryo dataformat. I now use JaxB to put classes in ActiveMQ, I'm worried with performances, I think such data format would be able to provide a faster alternative non intrusive alternative. Here the result of my comparison of Kryo vs JaxB (only marshalling/serialization, dataset of 1000 random generated classes which in XML are each one 480 nodes in average, with about 1,2 attributes per node). Testing JaxB Marshalling Total Time: 1.186 seconds Total Size: 37689851 (string length) Testing Serialization with Kryo Total Time: 0.216 seconds Total Size: 3674796 (bytes) Checking Serialization with Kryo Checked 1000 classes, 1000 instances, 1000 marshalled strings (in this last test I've verified the classes serialized/deserialized with Kryo comparing them as marshalled XML string with .equals() )
Body type problem on CXF component with CXF_MESSAGE dataFormat`
Hi All: I have a question about the expect body type of CXF compoent when using CXF_MESSAGE dataFormat. My CXF version is 2.7.5 and Camel version is 2.10.4. for example, I have a route:timer - setBody (constant string content) - CXF It works fine, if dataFormat of this cxf component is RAW, POJO or PAYLOAD, But, if dataFormat is CXF_MESSAGE, then the output request body is always empty, In order to make it work, I have to append a convertBodyTo component: timer - setBody (constant string content) - convertBodyTo (javax.xml.transform.Source.class) - CXF I checked the code, the Source type is required in method handleMessage of org.apache.cxf.jaxws.interceptors.MessageModeOutInterceptor.MessageModeOutInterceptorInternal As my understand, if the Source type is required, then this should be done inside Camel. else user may don't understand what's wrong. -- Thanks GangLiu MSN: liugang_0...@hotmail.com Skype: gang.liu.talendbj
Re: ActiveMQ Component: Stop route when no more messages are being received
You can use the inflight repository to know how many in-flight messages a route has. http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/InflightRepository.html On Mon, Jun 3, 2013 at 4:24 PM, Okello Nelson cn.oke...@gmail.com wrote: Hi Guys, I've been trying to work on this. Time has been hard to come by though. Having thought hard about a potential solution, i think using timer component would be the way to go. When period on the timer elpases, i retrieve the number of exchanges at the endpoints of interest. A timer route like: from(timer://controller?fixedRate=trueperiod=5000).to(ref:routesManager) I retrieve exchanges count in the routesManager bean. Now, my problem is that i still don't know how to retrieve the count of exchanges at an endpoint. Any assistance here will be appreciated very much. BTW: I've also posted this question at stackoverflow.com ( stackoverflow.com/questions/16898646/exchanges-count-at-camel-endpoint). On May 30, 2013 4:48 PM, Okello Nelson cn.oke...@gmail.com wrote: Hi Guys, I'm wondering how to stop an ActiveMQ route and start another one when it's nolonger receiving exchanges. I'm thinking that I probably need to use timeouts, but I'm not sure how to proceed. I've done some research but no success so far. Anyone with a solution, please assist. Kind Regards, Okello Nelson. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Camel always sending MQRFH2 headers to target WebsphereMQ queue.
Does this help? http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.doc%2Fmi21980_.htm 2013/6/3 shashi.kant shashiski...@gmail.com I have been trying to send message to a IBM websphere MQ queue which has to be in IBM500 charset, MQFMT_STRING format and encoding 273 from a Camel 2.10.4 application running on jboss. tried General ways of setting the connectionfactory properly with following values: connection.setTransportType(JMSC.MQJMS_CLIENT_NONJMS_MQ); connection.setStringProperty(WMQConstants.JMS_IBM_CHARACTER_SET, 500); connection.setStringProperty(WMQConstants.JMS_IBM_FORMAT, MQC.MQFMT_STRING); connection.setIntProperty(WMQConstants.JMS_IBM_ENCODING, 273); connection.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, WMQConstants.WMQ_CLIENT_NONJMS_MQ); I have tried IBMWebSphereMqDestinationResolver https://jira.springsource.org/secure/attachment/12688/IBMWebSphereMqDestinationResolver.java But everytime at the Websphere MQ end MQRFH2 header is there. I can't figure out any solution to this problem.. Somebody please help me out. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725.html Sent from the Camel - Users mailing list archive at Nabble.com. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: Camel without Spring. Limitations?
There is one limitation until now when you need to work with Camel Transactional Routes as Camel uses TransactionErrorHandler ( http://camel.apache.org/transactionerrorhandler.html). This TxErrorHandler uses behind the scene Spring to handle the Transactions and need to be changed in the future to become pluggable and able to run with Spring, Blueprint, CDI. On Tue, Jun 4, 2013 at 8:04 AM, Willem Jiang willem.ji...@gmail.com wrote: Camel and CXF support Blueprint which can do the same thing as Spring does. Did you have a chance to try it? 发自我的 iPhone 在 2013-6-3,下午6:59,Jose jagavi...@gmail.com 写道: Hi, I am trying to use Camel without Spring and I am wondering if there are some limitations. I guess the configuration would be more complicated but I wonder if I will loose some features. In particular, I am planning to use Camel with CXF. All the examples that I have seen use Camel with Spring. Thanks a lot. Jose -- View this message in context: http://camel.465427.n5.nabble.com/Camel-without-Spring-Limitations-tp5733686.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: camel-xmljson
Hi Surendra, My tests show that the underlying json-lib is very sensitive to whitespaces in the input XML. Removing inter-element whitespaces / XML indentation / pretty-print does the trick. So if you marshal this XML into JSON: rootapsalertthis is a test message/alert/apskey3value3/key3key2value2/key2key1value1/key1/root You get: {root:{aps:{alert:this is a test message},key3:value3,key2:value2,key1:value1}} You can remove XML indentation by running an identity XSLT with xsl:output indent=no. Hope that helps, *Raúl Kripalani* Enterprise Architect, Open Source Integration specialist, Program Manager | Apache Camel Committer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Mon, Jun 3, 2013 at 7:33 PM, Surendra surendrapam...@hotmail.com wrote: Thank you. Date: Mon, 3 Jun 2013 08:53:18 -0700 From: ml-node+s465427n5733722...@n5.nabble.com To: surendrapam...@hotmail.com Subject: Re: camel-xmljson I'll take a look at it later. Regards, *Raúl Kripalani* Enterprise Architect, Open Source Integration specialist, Program Manager | Apache Camel Committer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Mon, Jun 3, 2013 at 4:02 PM, Surendra [hidden email] wrote: Did anybody came across this issue? any clues? -- View this message in context: http://camel.465427.n5.nabble.com/camel-xmljson-tp5733645p5733712.html Sent from the Camel - Users mailing list archive at Nabble.com. If you reply to this email, your message will be added to the discussion below: http://camel.465427.n5.nabble.com/camel-xmljson-tp5733645p5733722.html To unsubscribe from camel-xmljson, click here. NAML -- View this message in context: http://camel.465427.n5.nabble.com/camel-xmljson-tp5733645p5733742.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel always sending MQRFH2 headers to target WebsphereMQ queue.
Not a advanced user .. i have seen that link before. can't figure out how do just that from camel. If u can just give some idea regarding that *Shashi Kant * ***Think positive and find fuel in failure* *+917259733668 * http://thinkndoawesome.blogspot.com/ *System/Software Engineer* *Hewlett-Packard India Software Operations. * On Tue, Jun 4, 2013 at 2:55 PM, David J. M. Karlsen [via Camel] ml-node+s465427n5733784...@n5.nabble.com wrote: Does this help? http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.doc%2Fmi21980_.htm 2013/6/3 shashi.kant [hidden email]http://user/SendEmail.jtp?type=nodenode=5733784i=0 I have been trying to send message to a IBM websphere MQ queue which has to be in IBM500 charset, MQFMT_STRING format and encoding 273 from a Camel 2.10.4 application running on jboss. tried General ways of setting the connectionfactory properly with following values: connection.setTransportType(JMSC.MQJMS_CLIENT_NONJMS_MQ); connection.setStringProperty(WMQConstants.JMS_IBM_CHARACTER_SET, 500); connection.setStringProperty(WMQConstants.JMS_IBM_FORMAT, MQC.MQFMT_STRING); connection.setIntProperty(WMQConstants.JMS_IBM_ENCODING, 273); connection.setIntProperty(WMQConstants.WMQ_CONNECTION_MODE, WMQConstants.WMQ_CLIENT_NONJMS_MQ); I have tried IBMWebSphereMqDestinationResolver https://jira.springsource.org/secure/attachment/12688/IBMWebSphereMqDestinationResolver.java But everytime at the Websphere MQ end MQRFH2 header is there. I can't figure out any solution to this problem.. Somebody please help me out. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725.html Sent from the Camel - Users mailing list archive at Nabble.com. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- If you reply to this email, your message will be added to the discussion below: http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725p5733784.html To unsubscribe from Camel always sending MQRFH2 headers to target WebsphereMQ queue., click herehttp://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5733725code=c2hhc2hpc2tpbGxzQGdtYWlsLmNvbXw1NzMzNzI1fC0xNDMxMTY0MTkx . NAMLhttp://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://camel.465427.n5.nabble.com/Camel-always-sending-MQRFH2-headers-to-target-WebsphereMQ-queue-tp5733725p5733790.html Sent from the Camel - Users mailing list archive at Nabble.com.
SPeL in tag attributes when using Spring context
Hi All, I'm trying to configure routes using spring context based on examples from here: http://camel.apache.org/spring.html It seems that it is not possible to use SPeL in certain fields, for example I try to specify uri as follows: camelContext xmlns=http://camel.apache.org/schema/spring; route id=inside from uri=#{ 'direct:inside' + uniqueNumber }/ ... /route /camelContext SPeL in the uri field is never executed and is used as is. Would it be possible to allow for it? Ivan. -- View this message in context: http://camel.465427.n5.nabble.com/SPeL-in-tag-attributes-when-using-Spring-context-tp5733794.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: SPeL in tag attributes when using Spring context
Hi No this is not possible in the from. You can use property placeholders. Or use java code or some programming language to do it. XML is not a programming language so it has limitation. And for dynamic uris, then you can do it in to as this FAQ shows how to do it http://camel.apache.org/how-do-i-use-dynamic-uri-in-to.html On Tue, Jun 4, 2013 at 3:11 PM, ikoblik ikob...@hotmail.com wrote: Hi All, I'm trying to configure routes using spring context based on examples from here: http://camel.apache.org/spring.html It seems that it is not possible to use SPeL in certain fields, for example I try to specify uri as follows: camelContext xmlns=http://camel.apache.org/schema/spring; route id=inside from uri=#{ 'direct:inside' + uniqueNumber }/ ... /route /camelContext SPeL in the uri field is never executed and is used as is. Would it be possible to allow for it? Ivan. -- View this message in context: http://camel.465427.n5.nabble.com/SPeL-in-tag-attributes-when-using-Spring-context-tp5733794.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Add routes to existing Camel context using Spring
Hi All, Is it possible to add routes to existing spring context? All examples [1] show how to declare routes and then create Camel Context with them, I could not find any example of how to do it in the reverse order. Thank you, Ivan. [1] http://camel.apache.org/spring.html -- View this message in context: http://camel.465427.n5.nabble.com/Add-routes-to-existing-Camel-context-using-Spring-tp5733797.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Add routes to existing Camel context using Spring
Hi See this cookbook example http://camel.apache.org/loading-routes-from-xml-files.html On Tue, Jun 4, 2013 at 3:20 PM, ikoblik ikob...@hotmail.com wrote: Hi All, Is it possible to add routes to existing spring context? All examples [1] show how to declare routes and then create Camel Context with them, I could not find any example of how to do it in the reverse order. Thank you, Ivan. [1] http://camel.apache.org/spring.html -- View this message in context: http://camel.465427.n5.nabble.com/Add-routes-to-existing-Camel-context-using-Spring-tp5733797.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: How to build a nested content based router?
Thank you very much! I see! -- View this message in context: http://camel.465427.n5.nabble.com/How-to-build-a-nested-content-based-router-tp5733708p5733799.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Add routes to existing Camel context using Spring
Hello Claus, Thank you for quick replies! Linked example looks interesting but I'd have to fall back to Java which is a pity if you try to stick to XML for configuration. Maybe I can come up with a pseudo bean that would add routes to the existing context? I'll post here if I decide to go this way. Ivan. -- View this message in context: http://camel.465427.n5.nabble.com/Add-routes-to-existing-Camel-context-using-Spring-tp5733797p5733800.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: the namespace on the IReportServiceExecuteRequest element, is not a valid SOAP version
Here is my code: Exchange exchange = template.send(cxf:bean:xdrReceiverEndpoint?synchronous=trueexchangePattern=InOut, new Processor() { public void process(final Exchange exchange) throws Exception { ListSource elements = new ArrayListSource(); elements.add(new DOMSource(DOMUtils.readXml(new StringReader(REQ_MESSAGE)).getDocumentElement())); CxfPayloadSoapHeader body = new CxfPayloadSoapHeader(new ArrayListSoapHeader(), elements, null); logger.debug(constructed cxfpayload body, +body); exchange.getIn().setBody(body); logger.debug(set body in exchange); exchange.getIn().addAttachment(REQ_DOC_CID, new DataHandler(new ByteArrayDataSource(docContent, UTF-8))); logger.debug(added attachment to exchange); //exchange.getIn().setHeader(CxfConstants.OPERATION_NAMESPACE, http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com;); // exchange.getIn().setHeader(CxfConstants.OPERATION_NAME, submitCcda); // logger.debug(added header); } } ); logger.debug(made the call to cxf endpoint); logger.debug(has out=+exchange.hasOut()); org.apache.camel.Message response = exchange.getOut(); logger.debug(received the response back, now decode it); logger.debug(response = +response); String value = decodeResponseFromPayload((CxfPayload?)response.getBody(CxfPayload.class), exchange); logger.debug(value = +value); body is null in the response so it fails in decodeResponseFromPayload method logs say: 2013-06-04 09:08:05 DEBUG constructed cxfpayload body, org.apache.camel.component.cxf.CxfPayload headers: []body: [ [ccdaRequest xmlns=http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService;clinicalDocumentccDocumentxop:Include xmlns:xop=http://www.w3.org/2004/08/xop/include; href=cid:cedoc//ccDocument/clinicalDocument/ccdaRequest]] [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:05 DEBUG set body in exchange [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:05 DEBUG added attachment to exchange [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG made the call to cxf endpoint [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG has out=true [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG received the response back, now decode it [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG Creating instance of bean 'org.apache.camel.converter.jaxp.DomConverter' [org.springframework.beans.factory.support.DefaultListableBeanFactory] 2013-06-04 09:08:06 DEBUG Finished creating instance of bean 'org.apache.camel.converter.jaxp.DomConverter' [org.springframework.beans.factory.support.DefaultListableBeanFactory] 2013-06-04 09:08:06 DEBUG response = Message: org.apache.camel.component.cxf.CxfPayload headers: []body: null [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG in decodeResponseFromPayload [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 DEBUG payload = org.apache.camel.component.cxf.CxfPayload headers: []body: null [com.ge.hcit.pil.xdrreceiverimpl.utils.XDRResponseHelper] 2013-06-04 09:08:06 INFO Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@3956267d: startup date [Tue Jun 04 09:08:06 CDT 2013]; root of -- View this message in context: http://camel.465427.n5.nabble.com/the-namespace-on-the-IReportServiceExecuteRequest-element-is-not-a-valid-SOAP-version-tp5284067p5733801.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Add routes to existing Camel context using Spring
This simple static function solves the issue for me: public static CamelContext addRoute(CamelContext camelContext, RouteBuilder routeBuilder) throws Exception { Preconditions.checkNotNull(camelContext, Utils.NPE_TEMPLATE, Camel context); Preconditions.checkNotNull(routeBuilder, Utils.NPE_TEMPLATE, Route builder); camelContext.addRoutes(routeBuilder); return camelContext; } Which I use from spring context like that: bean class=...CamelBootstrap factory-method=addRoute constructor-arg index=0 ref=camelContext / constructor-arg index=1 ref=newRoute / /bean It's not very pretty but it allows me to stay in XML for configuration. -- View this message in context: http://camel.465427.n5.nabble.com/Add-routes-to-existing-Camel-context-using-Spring-tp5733797p5733802.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Jetty - Performance Issue
Thank you, let me make this change and run the Load Test again.. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Jetty-Performance-Issue-tp5733133p5733809.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Jetty - Performance Issue
Hi, I would look out in my code for any new instance of the producerTemplate being created and inject as mentioned in your post. I would run the Load Test again and keep you posted. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Jetty-Performance-Issue-tp5733133p5733810.html Sent from the Camel - Users mailing list archive at Nabble.com.
Setting a requestTimeout for a shared/Exclusive reply does not take effect for multiple concurrent users
Setting requestTimeout of 1 second and receiveTimeout of 250 milliseconds timing out right after 1 second for a single request if there is no response. But if I fire multiple concurrent requests, then it's again waiting indefinitely rather than timing out (for both SHARED/EXCLUSIVE modes). Please clarify the following, 1. Why is it not timing out for more concurrent requests? 2. Why is it executing it in Async mode when it's configured as false (Refer the stack trace below)? From tomcat thread dump, all threads are waiting in CountDownLatch.await though we are NOT using async mode. Queue Config: jms:queue:QUEUE.REQUEST?replyTo=SYNC.REPLY?useMessageIDAsCorrelationID=truereceiveTime=1000preserveMessageQos=truereplyToType=ShareddisableReplyTo=false Stack trace from thread dump: ajp-bio-8010-exec-349 daemon prio=10 tid=0x05eaf000 nid=0x73f9 waiting on condition [0x54758000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) parking to wait for 0xbe675930 (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:115) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:86) at org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:63) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:360) at org.apache.camel.impl.ProducerCache$2.doInProducer(ProducerCache.java:331) at org.apache.camel.impl.ProducerCache.doInProducer(ProducerCache.java:227) at org.apache.camel.impl.ProducerCache.sendExchange(ProducerCache.java:331) at org.apache.camel.impl.ProducerCache.send(ProducerCache.java:186) at org.apache.camel.impl.DefaultProducerTemplate.send(DefaultProducerTemplate.java:115) at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:119) at org.apache.camel.impl.DefaultProducerTemplate.sendBody(DefaultProducerTemplate.java:136) at org.apache.camel.impl.DefaultProducerTemplate.requestBody(DefaultProducerTemplate.java:284) -- View this message in context: http://camel.465427.n5.nabble.com/Setting-a-requestTimeout-for-a-shared-Exclusive-reply-does-not-take-effect-for-multiple-concurrent-us-tp5733811.html Sent from the Camel - Users mailing list archive at Nabble.com.
Transactional test assertions timing issue
When unit (integration) testing a transacted route, such as (pseudo): route from uri=activemq:some queue/ transacted/ camel:process ref=someBeanProcessor/ /route Where someBeanProcessor does some DB work and participates in a JTA transaction with the JMS message on this route The problem is, what is a reliable way to apply an assertion on the work that someBeanProcessor has done in the DB? I've tried both of the following: 1. Add to: uri=log:some.logger.success?level=DEBUG/, get a MockEndpoint ref and use an expected message count of 1, and wait on mock.assertIsSatisified() 2. Use a NotifyBuilder on the route and use whenComplete(1), and wait on builder.matchesMockWaitTime() Both have the same result, where my test code is told about the success before the JTA transaction has finished comitting, so when the test thread performs a SQL select, it is doing so too early since the JTA tx of the route hasn't actually completed. This scenario works OK if the end result is something like to uri=activemq:out queue/ and I use a MockEndpoint on the JMS output URI, which makes sense since it'd be waiting on the TX to commit here; but what about routes where this isn't an option? Do I just need to suck it up and use Thread.sleep(..) on the test thread? Thanks, -- Alexander Sherwin
Quick question on Exchange
Hi All, at the end of a route I process exchanges coming from a CxfEndpoint. Until now I had only InOut exchanges, of which I process the input and set the getOut().setBody(...) to the new value (which goes back to the client). Now I have also a InOnly exchange, of which I process the input only but I leave untouched. As I'm at the end of the route, should I do something to notify the processing of the exchange is completed? I've remember vaguely of a complete flag somewhere in the documentation of Camel I've studied, but I've not found anything on the Exchange interface... Thank you! Cristiano
Re: Quick question on Exchange
the end of the route will handle that for you...if you need to explicitly stop the Exchange processing before the end of the route, you can do this by setting exchange.setProperty(Exchange.ROUTE_STOP, Boolean.TRUE)... Cristiano Costantini wrote Hi All, at the end of a route I process exchanges coming from a CxfEndpoint. Until now I had only InOut exchanges, of which I process the input and set the getOut().setBody(...) to the new value (which goes back to the client). Now I have also a InOnly exchange, of which I process the input only but I leave untouched. As I'm at the end of the route, should I do something to notify the processing of the exchange is completed? I've remember vaguely of a complete flag somewhere in the documentation of Camel I've studied, but I've not found anything on the Exchange interface... Thank you! Cristiano - Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Quick-question-on-Exchange-tp5733817p5733818.html Sent from the Camel - Users mailing list archive at Nabble.com.
how to pass an XML string to the unmarshal in the route definition
Hello I have the exchange body as a hashmap The hashmap has several key, value pairs, of which one needs to be unmarshalled. How can I pass that particular value (which is XML String) to the unmarshal In the following route from(INB_Q_URI) .routeId(ROUTE_ID_INB_RID) .log( START -) .unmarshal(jaxb) -thank you
Re: Quick question on Exchange
Yes! I was confused and scared to be missing something, Thank you! 2013/6/4 boday ben.o...@initekconsulting.com the end of the route will handle that for you...if you need to explicitly stop the Exchange processing before the end of the route, you can do this by setting exchange.setProperty(Exchange.ROUTE_STOP, Boolean.TRUE)... Cristiano Costantini wrote Hi All, at the end of a route I process exchanges coming from a CxfEndpoint. Until now I had only InOut exchanges, of which I process the input and set the getOut().setBody(...) to the new value (which goes back to the client). Now I have also a InOnly exchange, of which I process the input only but I leave untouched. As I'm at the end of the route, should I do something to notify the processing of the exchange is completed? I've remember vaguely of a complete flag somewhere in the documentation of Camel I've studied, but I've not found anything on the Exchange interface... Thank you! Cristiano - Ben O'Day IT Consultant -http://consulting-notes.com -- View this message in context: http://camel.465427.n5.nabble.com/Quick-question-on-Exchange-tp5733817p5733818.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: No bean named 'CamelBeanParameterMappingStrategy' is defined
Thank you for your answer. Do you know where it gets instantiated and which class is referring to it? - Alireza Salemi -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-named-CamelBeanParameterMappingStrategy-is-defined-tp5733753p5733821.html Sent from the Camel - Users mailing list archive at Nabble.com.
Issues with ftp in the 2.11.0 version of camel.
I am having performance issues with the ftp component in the 2.11.0 version of camel. When I load the camel xml route below in 2.10.4 it downloads the files quickly(5-10 seconds for 5 files), but in the 2.11.0 version it is really slow(minutes for 5 files) routes xmlns=http://camel.apache.org/schema/spring; route id=testftp from uri=ftp://ftp/temp?username=ftpuseramp;password=ftpuseramp;delay=3amp;delete=falseamp;idempotent=trueamp;include=.*.gzamp;stepwise=falseamp;consumer.maxMessagesPerPoll=5amp;eagerMaxMessagesPerPoll=false/ to uri=mock:foo / /route /routes -- View this message in context: http://camel.465427.n5.nabble.com/Issues-with-ftp-in-the-2-11-0-version-of-camel-tp5733824.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: A little problem with annotation @CsvRecord
Hi guys, I´m using camel bindy 2.8.0-fuse-07-16 in equinox I tried some of the solutions in this post, but without good results. I´m still getting java.lang.IllegalArgumentException: The separator has not been defined in the annotation @CsvRecord or not instantiated during initModel. must be specified Last try was with getting the object from the context, because other examples think applies to newer releases. Any clue about what can I try?, It´s possible that in osgi (equinox) really is not getting the separator ? @CsvRecord(separator = ,) thanks, Walter -- View this message in context: http://camel.465427.n5.nabble.com/A-little-problem-with-annotation-CsvRecord-tp5728109p5733825.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: No bean named 'CamelBeanParameterMappingStrategy' is defined
I don't know which version of camel you are using. But you can try to use class org.apache.camel.component.bean.DefaultParameterMappingStrategy -- 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, June 5, 2013 at 2:24 AM, salemi wrote: Thank you for your answer. Do you know where it gets instantiated and which class is referring to it? - Alireza Salemi -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-named-CamelBeanParameterMappingStrategy-is-defined-tp5733753p5733821.html Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Sending to remote WMQ queue.
Hello- I just saw this message on the Camel mailing list and wanted to let you know that we have a solution for processing MQ XMIT messages from Transmit queues. If you are still in need of a solution, let me know. Thanks! Matt Pavlovich Founding Partner Media Driver P: (512) 284-4330 E: m...@mediadriver.com Skype: mattrpav On Aug 10, 2012, at 2:39 AM, Caa_man c...@acs-it.ru wrote: We use transmissions queues, not remote. I.e. we dynamically build remote addresses. Could you help me? -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-remote-WMQ-queue-tp5717052p5717112.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: No bean named 'CamelBeanParameterMappingStrategy' is defined
Camel 2.10 - Alireza Salemi -- View this message in context: http://camel.465427.n5.nabble.com/No-bean-named-CamelBeanParameterMappingStrategy-is-defined-tp5733753p5733832.html Sent from the Camel - Users mailing list archive at Nabble.com.