Re: Non-extensible third-party class requires copied code from ASL licensed source

2012-02-27 Thread Christian Müller
Hello Valeri! Don't worry, you didn't waste my time. I also learned a few thinks. Jeff "kicked me" ;o) to work a bit hard to find a solution and asked for this kind of questions. And by the way, Roy's answer was (only for the next time when we don't find a better solution...): From: Roy T. Fie

Re: [DISCUSS] Camel 2.9.1 Release

2012-02-27 Thread Christian Müller
If it's considered as bug or improvement, I would like to fix [1]. It's an issue we hit last week in our development team and have to use a ugly workaround... [1] http://camel.465427.n5.nabble.com/DefaultUnitOfWork-doesn-t-copy-headers-from-the-original-message-if-it-s-a-JmsMessage-td5518546.html

Re: About Camel source which doesn't build under Maven 3.0.4

2012-02-27 Thread Daniel Kulp
Or suggestion number 3: 3) Flip to using the more recently maintained version of MSV at the new coordinates in central at: net.java.dev.msv msv-core That's what CXF did long ago. :-) Dan On Sunday, February 26, 2012 11:44:56 AM Babak Vahdat wrote: > Hi > > If y

Re: Non-extensible third-party class requires copied code from ASL licensed source

2012-02-27 Thread David Valeri
Christian, I was reviewing the Spring code again to answer your questions and I think I arrived at a solution that won't require copying. I misunderstood the inheritance mechanism used by Spring with respect to their testing related annotations and I have found an acceptable compromise solutio

Re: New Article posted on Camel

2012-02-27 Thread Richard Kettelerij
Hi, Nice blog, i've added a link to the articles page (http://camel.apache.org/articles). It takes some time to sync the wiki contents with the published website so it might not be visible immediately. Regards, Richard Blog: http://richardlog.com Twitter: http://twitter.com/rkettelerij --

Re: [DISCUSS] Camel 2.9.1 Release

2012-02-27 Thread Hadrian Zbarcea
Thank Chris, looking into it. Hadrian On 02/27/2012 09:56 AM, chris snow wrote: https://issues.apache.org/jira/browse/CAMEL-5030 would be good :) Although it's tagged as an improvement, the patch could be considered a fix as the 2.9.0 version of smpp doesn't work in my environment due to its la

Re: [DISCUSS] Camel 2.9.1 Release

2012-02-27 Thread chris snow
https://issues.apache.org/jira/browse/CAMEL-5030 would be good :) Although it's tagged as an improvement, the patch could be considered a fix as the 2.9.0 version of smpp doesn't work in my environment due to its lack of proxy support. On Mon, Feb 27, 2012 at 2:32 PM, Hadrian Zbarcea wrote: > Y

Re: [DISCUSS] Camel 2.9.1 Release

2012-02-27 Thread Hadrian Zbarcea
Yeah, got busy with other things :(. I am looking at last small fixes we can do in 2.9.x and build the kits probably on Wed. The builds were ok last week we should be in good shape. The jenkins builds only show one failure which I believe to be a test issue, but I'll look into it anyway. If an

Re: DefaultUnitOfWork doesn't copy headers from the original message if it's a JmsMessage

2012-02-27 Thread Babak Vahdat
Hi Christian, I did verify it as well and indeed copying headers would also work even if we deal with JmsMessage as well. However I've got no idea about the comment: // cannot copy headers with a JmsMessage as the underlying javax.jms.Message object goes nuts Which came across the revision [1].

DefaultUnitOfWork doesn't copy headers from the original message if it's a JmsMessage

2012-02-27 Thread Christian Müller
Hello! In DefaultUnitOfWork (line 86 -93) we have the following code: if (exchange.getIn().getClass().getSimpleName().equals("JmsMessage")) { this.originalInMessage = new DefaultMessage(); this.originalInMessage.setBody(exchange.getIn().getBody()); // c