Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A74DF1099A for ; Wed, 20 Nov 2013 11:10:35 +0000 (UTC) Received: (qmail 2936 invoked by uid 500); 20 Nov 2013 11:10:35 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 2622 invoked by uid 500); 20 Nov 2013 11:10:29 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 2593 invoked by uid 99); 20 Nov 2013 11:10:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 11:10:27 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 11:10:22 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Vj5fT-0004lt-64 for dev@camel.apache.org; Wed, 20 Nov 2013 03:09:59 -0800 Date: Wed, 20 Nov 2013 03:09:59 -0800 (PST) From: Babak Vahdat To: dev@camel.apache.org Message-ID: <1384945799155-5743570.post@n5.nabble.com> In-Reply-To: References: <5281275D.7050607@gmail.com> <2AAE57918709491992F984DFBA1B1B4F@gmail.com> <52896546.7020800@gmail.com> <528B8A50.7040403@gmail.com> Subject: Re: [DISCUSS] - Apache Camel 2.12.2 release later this month? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi As working on CAMEL-6985 last night I spotted a bug concerning the blueprin= t based Camel apps. Following the steps to reproduce: - Install the Twitter-Websocket-Blueprint example into the Karaf and then make use of the 'route-info' command for it as below: ~/dev/apache-karaf-2.3.3/bin>./karaf clean __ __ ____ =20 / //_/____ __________ _/ __/ =20 / ,< / __ `/ ___/ __ `/ /_ =20 / /| |/ /_/ / / / /_/ / __/ =20 /_/ |_|\__,_/_/ \__,_/_/ =20 Apache Karaf (2.3.3) Hit '' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '' or type 'osgi:shutdown' or 'logout' to shutdown Karaf. karaf@root> features:chooseurl camel 2.13-SNAPSHOT adding feature url mvn:org.apache.camel.karaf/apache-camel/2.13-SNAPSHOT/xml/features karaf@root> features:install camel-blueprint camel-twitter camel-websocket karaf@root> osgi:install -s mvn:org.apache.camel/camel-example-twitter-websocket-blueprint/2.13-SNAPSHO= T Bundle ID: 85 karaf@root> route-info twitter-route=20 Camel Route twitter-route =09Camel Context: twitter-camel Properties =09id =3D twitter-route =09parent =3D 6493bb37 Statistics =09Inflight Exchanges: 0 =09Exchanges Total: 19 =09Exchanges Completed: 19 =09Exchanges Failed: 0 =09Min Processing Time: 0 ms =09Max Processing Time: 4 ms =09Mean Processing Time: 0 ms =09Total Processing Time: 14 ms =09Last Processing Time: 1 ms =09Delta Processing Time: 1 ms =09Load Avg: 0.00, 0.00, 0.00 =09Reset Statistics Date: 2013-11-20 11:53:55 =09First Exchange Date: 2013-11-20 11:53:57 =09Last Exchange Completed Date: 2013-11-20 11:54:02 Definition And as you see the XML namespace is wrong: http://camel.apache.org/schema/spring instead of http://camel.apache.org/schema/blueprint Actually this bug has nothing to do with the Karaf command itself but the way how our JAXB namespace is definded, as an example see: https://github.com/apache/camel/blob/master/camel-core/src/main/java/org/ap= ache/camel/model/package-info.java We also have got already a hack by camel-blueprint to fix up the XML namespace from spring to blueprint and vice versa which doesn't help here much (CamelNamespaceHandler#renameNamespaceRecursive). I think somehow we have to make the ModelHelper utility a bit more clever. BTW this bug seems to be there since ages. I have neither looked into this in detail nor raised a JIRA for it. Babak Claus Ibsen-2 wrote > Okay lets try to get this release out. >=20 > Its 2 months since the last patch release of 2.12.x was out. >=20 >=20 >=20 > On Tue, Nov 19, 2013 at 4:57 PM, Hadrian Zbarcea < > hzbarcea@ > > wrote: >> After Willem's fix last night all tests are now passing (with one >> intermittent test failure in camel-jms, I believe timing related). Pleas= e >> let me know today, what are the issues you're working on we must have in >> 2.12.2 so we could close down on the release. >> >> Thanks, >> Hadrian >> >> >> On 11/17/2013 07:54 PM, Hadrian Zbarcea wrote: >>> >>> There are test failure(s) I need to look at: >>> >>> Are there any other issues you absolutely need in 2.12.2? >>> >>> Hadrian >>> >>> >>> >>> >>> On 11/12/2013 08:11 PM, Willem jiang wrote: >>>> >>>> +1, >>>> BTW, it looks Camel 2.12.x is catch up the release cycle of Camel >>>> 2.11.x. >>>> >>>> >>>> -- >>>> Willem Jiang >>>> >>>> Red Hat, Inc. >>>> Web: 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: =E5=A7=9C=E5=AE=81willem >>>> >>>> >>>> >>>> >>>> >>>> On Wednesday, November 13, 2013 at 5:13 AM, Christian M=C3=BCller wrot= e: >>>> >>>>> +1 >>>>> >>>>> Best, >>>>> Christian >>>>> >>>>> >>>>> >>>>> On Tue, Nov 12, 2013 at 5:24 PM, Claus Ibsen < > claus.ibsen@ > >>>> (mailto: > claus.ibsen@ > )> wrote: >>>>> >>>>>> On Mon, Nov 11, 2013 at 7:52 PM, Hadrian Zbarcea < > hzbarcea@ > >>>>> (mailto: > hzbarcea@ > )> >>>>>> wrote: >>>>>>> >>>>>>> I wanted to say the same thing. Maybe even sooner in the month. How >>>>>>> about >>>>>>> shooting to build the release end of this week. I can take care of >>>>>>> this >>>>>>> release. >>>>>>> >>>>>>> Hadrian >>>>>> >>>>>> >>>>>> Yeah that works for me too. Just thought it was about time we cut a >>>>>> new patch release for the 2.12 branch now that we have 100+ jiras >>>>>> resolved. >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> On 11/11/2013 01:33 PM, Claus Ibsen wrote: >>>>>>>> >>>>>>>> >>>>>>>> Hi >>>>>>>> >>>>>>>> I think we should cut a new 2.12.2 release later this month. We >>>>>>>> have >>>>>>>> so far 115 jira's resolved. >>>>>>>> >>>>>>>> Any thoughts? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Claus Ibsen >>>>>> ----------------- >>>>>> Red Hat, Inc. >>>>>> Email:=20 > cibsen@ > (mailto: > cibsen@ > ) >>>>>> Twitter: davsclaus >>>>>> Blog: http://davsclaus.com >>>>>> Author of Camel in Action: http://www.manning.com/ibsen >>>>> >>>>> >>>> >>>> >>>> >> >=20 >=20 >=20 > --=20 > Claus Ibsen > ----------------- > Red Hat, Inc. > Email:=20 > cibsen@ > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apa= che-Camel-2-12-2-release-later-this-month-tp5743058p5743570.html Sent from the Camel Development mailing list archive at Nabble.com.