Re: Camel in Production

2009-04-15 Thread Martin Krasser
Hi Samarth, we're using Camel in the Open eHealth Integration Platform (IPF) [1]. IPF is deployed in clinical environments in Europe and US. The focus is on HL7 message processing and IHE profiles. IPF has also been tested successfully at the Connect-a-thon 2009[2] for the IHE profiles PIX and

Re: IBatis component inconsistency

2009-04-15 Thread Claus Ibsen
On Wed, Apr 15, 2009 at 7:24 PM, javadevel wrote: > > Clause, > > The fact that iBatis was sending an empty List (java.util.ArrayList) that > could be confused as a legitimate response by the camel router was pretty > obvious from the logs, I just thought that the camel iBatis component would > kn

Re: Camel in Production

2009-04-15 Thread Wilson
Hi Samarth, I've used Camel 1.3 in a enterprise project for the biggest Mobile Phone company in Brazil. The Camel ESB is able to exchange a huge amount of Data using complex routes and AciveMQ message exchange and persistence. The solution is running in production for several months... so far,

Camel in Production

2009-04-15 Thread samarthbhargava
Hi, I am evaluating Spring Integration, Camel & JBPM to implement workflows. I was looking for some case studies/projects that are using Camel and have deployed it in production. I would also like to know whether there are any performance benchmarks for Camel that can demonstrate the scalability

Re: IBatis component inconsistency

2009-04-15 Thread javadevel
Clause, The fact that iBatis was sending an empty List (java.util.ArrayList) that could be confused as a legitimate response by the camel router was pretty obvious from the logs, I just thought that the camel iBatis component would know about this and check to see weather the List is empty or not

Re: camel-soap: New WSDL SOAP client component

2009-04-15 Thread Claus Ibsen
Hi Wilson This looks very good. Nice and simple, I like that :) Keep up the good work and welcome on board the Camel ride. On Wed, Apr 15, 2009 at 3:13 PM, Wilson wrote: > > Hi, > > I am working on a SOAP client camel component. > > Using camel-soap the developer is not required to implement

Re: Quartz route with Spring transactions

2009-04-15 Thread Martin Gilday
Hi Claus, Yes it is 1.x. He had the policy set just as you say. We are thinking that the problem might be the way he has his test set up. We are using spring-test and so the Camel context is created outside of the test case and then injected in. We think there might be some threading issues du

Re: Quartz route with Spring transactions

2009-04-15 Thread Claus Ibsen
Hi I assume its Camel 1.x. You must use the .policy(required) stuff to indicate a route is transacted in Camel 1.x See the transactional client EIP for details. from(quartz://..).policy(required).to(springBean).to(springBean); It will commit if the exchange was processed with no exception. If a

Quartz route with Spring transactions

2009-04-15 Thread Martin Gilday
Hi, One of my colleagues is trying to create a transactional route which starts with a Quartz endpoint. However the transaction does not appear to start. If he replaces the Quartz endpoint with a Direct then the transaction works. He would like the whole route started by the Quartz endpoint to b

camel-soap: New WSDL SOAP client component

2009-04-15 Thread Wilson
Hi, I am working on a SOAP client camel component. Using camel-soap the developer is not required to implement a SEI or any kind of stub code. All you need to do is to provide: - WSDL location. - Web service address. - Operation to invoke. camel-soap consumes java.util.Map objects and conv