camel-example-cxf-tomcat class loader issue when deploys in WebSphere

2013-01-30 Thread Duke
Hi All, I am very new for Apache Camel. I downloaded the Apache Camel 2.10.3. I built the Apache Camel 2 example camel-example-cxf-tomcat by using the command "mvn clean package". I deployed to Tomcat. It works fine. However, my server target is WebSphere Application Server version 8.5. I read th

Re: Error running routes in Scala DSL with Scala v 2.10.0

2013-01-30 Thread glsilverman
Looks like this issue has already been discussed: http://camel.465427.n5.nabble.com/Scala-DSL-with-Scala-2-10-td5724331.html. Sorry for the duplication. -- View this message in context: http://camel.465427.n5.nabble.com/Error-running-routes-in-Scala-DSL-with-Scala-v-2-10-0-tp5726587p5726590.htm

Camel-Quickfixj 2.9.3 - Ordering issue

2013-01-30 Thread vcheruvu
Hello Camel Riders, I have used Camel-Quickfixj component in our application to consume and publish fix messages. Our application consumes FIX 4.2 messages from VM queue with 10 concurrent consumers. Each consumer takes the FIX message of the VM queue, transforms the message to our internal FI

Re: Error running routes in Scala DSL with Scala v 2.10.0

2013-01-30 Thread Babak Vahdat
Hi The Scala 2.10 support will start by the upcoming 2.11 Release, see here for the details: http://camel.apache.org/scala-dsl.html Babak glsilverman wrote > I created a maven project using the camel-scala-archetype archetype. > Running mvn exec:java works fine out-of-the box, but when I chan

Re: Configuring MINA Server Endpoint

2013-01-30 Thread Babak Vahdat
Am 30.01.13 21:25 schrieb "peter.berkman" unter : >I am configuring MINA via bean configuration, but the codec reference >keeps >throwing an excption: > >{code} > class="org.apache.camel.component.mina.MinaComponent"> > > > >factory-bean="pixpdqv2MinaF

Re: Question about change to FileUtil.java

2013-01-30 Thread Babak Vahdat
Am 30.01.13 21:57 schrieb "vishal1981" unter : >Thanks for the reply. Yes I did realize I could test against the snapshot >but our QA won't accept beta releases of a 3rd party jar :). No, what I meant was just to *temporarily* do that to see if the regression is really fixed and then after the

RE: Question about change to FileUtil.java

2013-01-30 Thread vishal1981
Thanks for the reply. Yes I did realize I could test against the snapshot but our QA won't accept beta releases of a 3rd party jar :). Anyways..I am now testing against 2.10.2. regards, -v- From: Babak Vahdat [via Camel] [mailto:ml-node+s465427n5726583...@n5.nabbl

Re: Question about change to FileUtil.java

2013-01-30 Thread Babak Vahdat
Maybe you could already verify if the regression you're facing has been really fixed by the upcoming 2.10.4 release. For this you would need to (temporarily) add the Apache Snapshot repository into your POM: http://camel.apache.org/download.html#Download-Maven2snapshotrepositoryinpom then depend

Configuring MINA Server Endpoint

2013-01-30 Thread peter.berkman
I am configuring MINA via bean configuration, but the codec reference keeps throwing an excption: {code}

Re: Question about change to FileUtil.java

2013-01-30 Thread Babak Vahdat
You're right. I get the same 404 as I get redirected to the swiss mirror here: http://mirror.switch.ch/mirror/apache/dist/camel/apache-camel/2.10.2/apache-camel-2.10.2.zip It seems the releases have not pushed properly into the mirrors. Have you tried to download directly from the central itself?

Re: Question about change to FileUtil.java

2013-01-30 Thread vishal1981
Hi, None of the mirrors seem to be working for 2.10.2. I keep getting 404. This has been the case with several other release for me. I am sure my connectivity is ok. I am able to download 2.10.3 just fine. I am downloading via, http://www.apache.org/dyn/closer.cgi/camel/apache-camel/2.10.2/apache-c

RE: Question about change to FileUtil.java

2013-01-30 Thread Vishal Changrani
Fyi - got a reply - http://camel.465427.n5.nabble.com/Question-about-change-to-FileUtil-java-tt5726527.html#a5726576 _ From: Vishal Changrani Sent: Tuesday, January 29, 2013 6:24 PM To: 'users@camel.apac

Re: Question about change to FileUtil.java

2013-01-30 Thread vishal1981
Ah ok so its only broken in 2.10.3. Great I will switch to 2.10.2. Thanks again. -- View this message in context: http://camel.465427.n5.nabble.com/Question-about-change-to-FileUtil-java-tp5726527p5726576.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Question about change to FileUtil.java

2013-01-30 Thread Claus Ibsen
On Wed, Jan 30, 2013 at 4:58 PM, vishal1981 wrote: > I do indeed use 2.10.3. May I know when is 2.10.4 anticipated? > You can use 2.10.2 in the mean time. 2.10.4 is scheduled for Feb/Mar 2013. > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Question-about-change-t

Re: Question about change to FileUtil.java

2013-01-30 Thread vishal1981
I do indeed use 2.10.3. May I know when is 2.10.4 anticipated? -- View this message in context: http://camel.465427.n5.nabble.com/Question-about-change-to-FileUtil-java-tp5726527p5726566.html Sent from the Camel - Users mailing list archive at Nabble.com.

Another question to concurrent consumer

2013-01-30 Thread zzkozak
Hi, giving this JmsConfiguraiton: I would expect, that if the queue "ordersOverview" will be filled with for example 10 messages, they would be processed in parallel, right? But the messages are processed synchronously AND if during processing of one message an OrderNotFoundException is thrown,

Re: camel-cxf in WebSphere without geronimo/jetty depdendencies - possible

2013-01-30 Thread Angelo
Could you explain why the cxf.xml import is required given the technique(s) I'm using to bootstrap these frameworks? I will definitely try to remove the jetty dependency today - top priority now that I got it working is to get rid of anything I don't absolutely need. -- View this message in co

Re: Scala DSL with Scala 2.10

2013-01-30 Thread Henryk Konsek
> The JAR name is camel-scala_2.9 and not camel-scala29. The directory > for the source code is camel-scala29. Actually I think that we could keep it in the current form, as this is deprecated module and will be soon removed from the version control. I'll just update the documentation. -- Henryk