Re: Article Java Magazin July 2014 on Apache Integration stack

Hi Neil and Communities, Good news! An (almost) 1:1 translation in English is available. Please contact me directly if you'd like a copy. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http:

CXF Endpoint accepts invalid SOAP-Envelope in POJO-Mode

Hello, we developed a webservice with cxf and camel. Everything works fine, except the fact that the cxf-endpoint accepts invalid SOAP-Messages. For example we have a SOAP-Message: http://schemas.xmlsoap.org/soap/envelope/";> ... ... But we observed that it

Try/Catch-like onException with Blueprint DSL

Hello, I am analyzing the Exception handling capabilities of Apache Camel and might have run into an inconsistency between the Java DSL and Blueprint, when using onException on a route-processor level. Due to several reasons, I do not want to use the doTry/doCatch handling, but the onException co

Re: Try/Catch-like onException with Blueprint DSL

On Fri, Jun 6, 2014 at 11:46 AM, dritter wrote: > Hello, > > I am analyzing the Exception handling capabilities of Apache Camel and might > have run into an inconsistency between the Java DSL and Blueprint, when > using onException on a route-processor level. > > Due to several reasons, I do not w

Async and UnitOfWork

Hi, I have a restlet route that triggers SEDA and VM routes. The unit of work is used to do some transformation of the result before it is sent to the HTTP client. It works fine as long as there is no SEDA or VM. As soon as the latter two are included, the unit of work is not executed anymore. Th

Re: Async and UnitOfWork

Hi You can set the synchronous option. See http://camel.apache.org/asynchronous-routing-engine.html On Fri, Jun 6, 2014 at 12:11 PM, Max Bridgewater wrote: > Hi, > > I have a restlet route that triggers SEDA and VM routes. The unit of work > is used to do some transformation of the result before

Re: Async and UnitOfWork

Hi Claus, Thanks for your input. Do you suggest to use synchronous flag on the SEDA and VM producers? They have a flag waitForTaskToComplete that I curretly set to Never. Indeed if I set these flags to Always, the processing becomes synchronous and everything works fine. The challenge is that th

Re: Try/Catch-like onException with Blueprint DSL

Thank you. It seemed to me that this was not the intended use. However, is there any chance to ensure the described/required behavior with Camel ("Do you know a way how to ensure the same behavior?")? The doTry/doCatch seems to be one way to achieve this. Unfortunately, it comes with several "unwa

Re: Async and UnitOfWork

Hi Maybe its the wire tap eip you should use. On Fri, Jun 6, 2014 at 12:38 PM, Max Bridgewater wrote: > Hi Claus, > > Thanks for your input. Do you suggest to use synchronous flag on the SEDA > and VM producers? They have a flag waitForTaskToComplete that I curretly > set to Never. Indeed if I

AggregationStrategy and completionPredicate

Hi list, I'm using the following aggregation: aggrId ${in.header.complId} == 'END_${exchangeId}' When the aggregation may be concluded I send an empty message with the 'complId' set to the expected value but currently I get: org.apache.camel.CamelExchangeExce

Re: CustomSoapFault Problem

the wsdl is ok, wsdl2java will generate MyWebServiceFault_Exception instead of MyWebServiceFault http://nono.com/"; name="MyWebService" xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsp="http://www.w3.org/ns/ws-policy"; xmlns:tns="http://nono.com/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema

Re: AggregationStrategy and completionPredicate

Hi See the aggregator docs http://camel.apache.org/aggregator2 there is an eagerCheckCompletion option On Fri, Jun 6, 2014 at 2:46 PM, carlo cancellieri wrote: > Hi list, > I'm using the following aggregation: > > > > > > aggregationRepositoryRef="aggregationRepository" > completionFromB

Fwd: AggregationStrategy and completionPredicate

Hi list, I'm using the following aggregation: aggrId ${in.header.complId} == 'END_${exchangeId}' When the aggregation may be concluded I send an empty message with the 'complId' set to the expected value but currently I get: org.apache.camel.CamelExchangeExcep

Re: AdviceWithRouteBuilder.weaveById() creates duplicated endpoint

Hi Feel free to log a JIRA ticket http://camel.apache.org/support Also maybe try some of the other weaveByXXX to see if any of those works. On Thu, Jun 5, 2014 at 4:40 PM, João Rodrigues wrote: > Hi, > I've tried camel 2.13.0 and it shows the same symptoms. > > Thanks > > > On Wed, Jun 4, 2014

Re: Best Efforts 1 PC pattern - from MQ to DB

Anyone having experience with IBM/WebSphere MQ? Shall I rely on WMQ Connection Factory caching or shall I rather configure Spring's CachingConnectionFactory? Thanks a lot, Dan -- View this message in context: http://camel.465427.n5.nabble.com/Best-Efforts-1-PC-pattern-from-MQ-to-DB-tp5751757p5

Re: AdviceWithRouteBuilder.weaveById() creates duplicated endpoint

Hi Claus, I've submitted the JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-7485 (hope its ok, that's my first ticket here at ASF). I've just updated the test case to include weaveByToString (same behavior of weaveById). Thanks On Fri, Jun 6, 2014 at 2:20 PM, Claus Ibsen wrote: > Hi

Re: Best Efforts 1 PC pattern - from MQ to DB

Someone once told me to avoid using Spring's connection factories with Camel. Not sure of the why though. JB On 6/6/14 10:14 AM, "dancsi" wrote: >Anyone having experience with IBM/WebSphere MQ? Shall I rely on WMQ >Connection Factory caching or shall I rather configure Spring's >CachingConnecti

Re: AggregationStrategy and completionPredicate

Dear Claus, I'm trying to use the suggested flag eagerCheckCompletion="true" with no success. I still get: org.apache.camel.CamelExchangeException: Invalid correlation key. Exchange[test_complete.csv] at org.apache.camel.processor.aggregate.AggregateProcessor.doProcess(AggregateProcessor.java:204

Re: AggregationStrategy and completionPredicate

You get an invalid correlation key, so check that. aggrId Do you have that header On Fri, Jun 6, 2014 at 4:37 PM, carlo cancellieri wrote: > Dear Claus, > I'm trying to use the suggested flag eagerCheckCompletion="true" with no > success. > I still get: > org.apache.camel.CamelExchangeEx

Re: AggregationStrategy and completionPredicate

Claus, > You get an invalid correlation key, so check that. > > > > aggrId > > Yes, I've added it to skip that error but the incoming (fake) exchange is still passed to the aggregation while what I need is to complete the aggregation without this message. It should be considered as a trigger

Re: AggregationStrategy and completionPredicate

On Fri, Jun 6, 2014 at 5:01 PM, carlo cancellieri wrote: > Claus, > >> You get an invalid correlation key, so check that. >> >> >> >> aggrId >> >> > > Yes, I've added it to skip that error but the incoming (fake) exchange is > still passed to the aggregation while what I need is to complete t

Re: Still waiting for shutdown of 1 message listener invokers

The route policy did help but I got another solution where we stop route by spawning another thread for route shutdown. This allowed route to gracefully shutdown. -- View this message in context: http://camel.465427.n5.nabble.com/Still-waiting-for-shutdown-of-1-message-listener-invokers-tp57517

Re: Still waiting for shutdown of 1 message listener invokers

Thank you. Spawning another thread to shutdown route did help. -- View this message in context: http://camel.465427.n5.nabble.com/Still-waiting-for-shutdown-of-1-message-listener-invokers-tp5751761p5752006.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Try/Catch-like onException with Blueprint DSL

Hello, maybe the onWhen() construct can help out here. The idea is to use the "CamelMessageHistory" to check for the last processor in the Camel route that was accessed, which is the failing one. The onWhen(...) construct is then used to catch the filtered exceptions. This could look similar to

Re: Best Efforts 1 PC pattern - from MQ to DB

We use only the IBM one and it works fine 6. Juni 2014 16:15 skrev "dancsi" følgende: > Anyone having experience with IBM/WebSphere MQ? Shall I rely on WMQ > Connection Factory caching or shall I rather configure Spring's > CachingConnectionFactory? > > Thanks a lot, > Dan > > > > -- > View this

Throttler

All, I am evaluating Camel to be a proxy/gateway to REST internal end points. I have set it up as a servlet on Tomcat and configured for http proxy and it is working. I also wanted to implement throttling rules using throttler. So, I have used the sample available in documentation to restrict

Re: Async and UnitOfWork

It would be interesting to implement asynch and share unit of work by way of futures in the ... well ... future. :) But currently you cant really do that. What you need are transactions. The problem is SEDA doesn't support transactions. So what you need is JMS. *Robert Simmons Jr. MSc. - Lead Java

Re: Async and UnitOfWork

I think wire tap actually serves me well. I have NOT verified that the execution of the SEDA route happens asynchronous when I set waitForTaskToComplete to Never. For now, I give it the benefit of the doubt ;). How would use futures be different from wire tapping? Thanks a lot. On Fri, Jun 6, 20

Re: Async and UnitOfWork

Futures allow asynch programming without waiting on a result that might take a while. If Camel supported them an exchange could collect futures and would only have to wait for the actual values when he contents of the futures were used. This would make for powerful asynch features. Look up Java Fu

Dynamic DataSource for SQL

Hello, I'm converting services written with IBM Message Broker 6.1 to Apache Camel. Here's some of the logic I'm trying to convert: SET Environment.Variables.dataSource = ''; CASE UPPER(InputRoot.XMLNSC.ns:memberLookupRequest.ns:args0.ax21:Client) WHEN 'client1' THEN SET Environment.Var

Hi

Thanks & Regards Yagyesh Kumar Mishra Mobile: 8800447897 " Ignorance is death, knowledge is life"