Re: A "Kamel" crazy idea

Jeff Genender, I and James Carman long ago were tossing around the idea of Ibex, it would have been a Scala based AKKA eco system for putting in routes. You’d just say run in this namespace, conform to these Actor roles and we compose the tree for you. What you propose is a bit easier and more t

Re: A "Kamel" crazy idea

I find it super +1 - If not only for your awesome narrative. > On Jul 12, 2018, at 5:30 PM, Nicola Ferraro wrote: > > Hi Cameleers, > it's now passed some time since I started thinking about a new project that > we can begin here at Apache Camel, and I'd like to have your opinion. > > We've a

Re: CamelSmppError=034,CamelSmppStatus=UNDELIV

I'm guessing from smsc error code tables that means invalid distribution list name. Sent from my pressure cooker. > On Oct 1, 2016, at 22:23, raju jwala wrote: > > Hi Team, > > I am facing issue in my application. > > My Application is using SMPP protocal and SMSC as gateway. > > I am getti

MSDN Licensing

For Apache Camel committers ; (Apache Committers as a total) https://s.apache.org/asf_msdn This is a license for the Microsoft Suite for you to use in ASF development and documentation. Your ASF login will determine eligibility, there might be some hiccups so ple

Re: [VOTE] Camel 2.17.3

+1 Sent from my pressure cooker. > On Aug 7, 2016, at 03:53, Jean-Baptiste Onofré wrote: > > +1 (binding) > > Regards > JB > > > >> On Aug 7, 2016, 08:41, at 08:41, Andrea Cosentino >> wrote: >> +1 (binding). >> >> Thanks Dan! >> -- >> Andrea Cosentino >> ---

Re: [DISCUSS] - Thoughts on Apache Camel 2.18 and towards 3.0

I think the core should focus on speed, consistency, reliability and last extensibility; Camel has a nice traction but we don’t want to see “strange” bugs from new features if that makes sense as a long windy sentence….. > On Apr 4, 2016, at 9:36 AM, Matt Pavlovich wrote: > > > > On 3/24/16

Re: [DISCUSS] Move to java 8 for 2.17?

Dan, I like that! /je > On Jan 29, 2016, at 12:30 PM, James Carman wrote: > > Proper Java8 support could give us quite an opportunity here. Marking our > interfaces as functional (not required of course) and designing our API to > be "lambda-friendly" > > On Fri, Jan 29, 2016 at 8:24 AM Daniel

Re: [DISCUSS] Move to java 8 for 2.17?

That sounds rather reasonable. > On Jan 28, 2016, at 11:13 AM, Claus Ibsen wrote: > > On Thu, Jan 28, 2016 at 3:48 PM, James Carman > wrote: >> I would rather us bump the major version number if we're going to start >> requiring users to use Java8. >> > > Yeah that was also my first thought.

Re: [DISCUSS] Move to java 8 for 2.17?

If we start using say Lambdas, then you are SOL on Java 7. Right? > On Jan 28, 2016, at 8:54 AM, Raul Kripalani wrote: > > On Thu, Jan 28, 2016 at 3:49 PM, Johan Edstrom wrote: > >> Well - that doesn’t hold true for Java8 language features, does it? >> > >

Re: [DISCUSS] Move to java 8 for 2.17?

Well - that doesn’t hold true for Java8 language features, does it? > On Jan 28, 2016, at 8:39 AM, Raul Kripalani wrote: > > Good point, James. But after spending over 6 years in 2.x, I think users > might expect a little more from 3.x than just a standard 2.x release + JDK > upgrade. So from t

Re: [DISCUSS] - Camel 2.12.5 and 2.13.3 releases

+1 Johan Edstrom - via HopOn October 2, 2014 at 23:54 GMT, Hadrian Zbarcea wrote:+1.That's pretty much what we always did. I think it warrants more an announcement than a discussion.Cheers,Hadrian

Re: [VOTE] Release Apache Camel 2.12.3

+1 On Feb 17, 2014, at 2:11 PM, Christian Schneider wrote: > +1 > > Christian > > Am 16.02.2014 05:16, schrieb Hadrian Zbarcea: >> This is a vote to release Apache Camel 2.12.3, a patch release coming with >> about 128 issues fixed. >> >> Release notes: >> https://issues.apache.org/jira/secu

Re: [VOTE] Release Apache Camel 2.11.4

I can't see what it stops, looks like cosmetics? +1 On Feb 16, 2014, at 4:07 PM, James Carman wrote: > Why not just mark the issue as not fixed and release? Is the issue a > show-stopper? > > On Sunday, February 16, 2014, Babak Vahdat > wrote: > >> -1 >> >> See >> >> http://camel.465427.n

Re: [VOTE] Release Apache Camel 2.11.3

+1 Sent from my pressure cooker. > On Jan 9, 2014, at 7:43, Willem Jiang wrote: > > I ran the unit tests of camel in action (after changing activemq and spring > version), the kit looks good. > > Here is my +1. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: h

Re: Can I use camel-nagios to get nagios's information when I send passive check through it?

Same purpose as sending udp would have in networking. Sent from my pressure cooker. On Dec 16, 2013, at 18:19, gigglesun wrote: > Thank you very much. I am wondering since camel-nagios can't get message > from the nagios server, how could a programmer know whether his\her request > has been suc

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

Benjamin, it has been discussed in AMQ as well. http://irclogs.dankulp.com/logs/irclogger_log/activemq/?date=2013-11-13,Wed http://irclogs.dankulp.com/logs/irclogger_log/activemq/?date=2013-10-25,Fri On Dec 1, 2013, at 11:03 AM, Benjamin Graf wrote: > Hi > > BTW why is hawtio a problem for Ca

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

Babak, the good thing about personal opinion and ad-hominem attacks it that one doesn't have to share them. On Dec 1, 2013, at 11:03 AM, Benjamin Graf wrote: > Hi > > BTW why is hawtio a problem for Camel for political reason? It is yet the > official front end for ActiveMQ. Is this seen diff

Re: [DISCUSS] Remove the camel:dot goal

+1 Sent from my pressure cooker. On Nov 28, 2013, at 21:19, Tracy Snell wrote: > +1 > > On Nov 28, 2013, at 9:08 PM, Hadrian Zbarcea wrote: > >> The camel:dot goal provided by the camel-maven-plugin has not been >> maintained in 5+ years, produces poor quality output and, most importantly,

Re: CAMEL-6694 Getting hold of the Context ClassLoader from deep within

I really don't want classloader dinking. On Nov 19, 2013, at 7:19 PM, Willem jiang wrote: > You can get the CamelContext from the Exchange which can be accessed from > CamelLogProcessor. > But I’m not sure if the setting the TCCL can resolve the issue of CAMEL-6694. > > > -- > Willem Jiang

Re: git commit: Upgrade to leveldbjni 1.8

Would this have gone in had it been a regular git hub project? That's really the only question you need to ask yourself, right? Sent from my pressure cooker. On Oct 18, 2013, at 18:25, Christian Müller wrote: > I'm sure you know the project much better than me, but if you have a look > at the d

Re: [VOTE] Release Apache Camel 2.10.7

+1 On Sep 16, 2013, at 7:49 AM, j...@nanthrax.net wrote: > +1 (non binding) > > Regards > JB > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://wwx.talend.com > > - Reply message - > From: "Jon Anstey" > To: > Subject: [VOTE] Release Apac

Re: Camel toolbox for frequently used pieces of logic

Just my 2 cents... I tend to focus more on Camel as a library and much less on it as an EIP engine or runtime. I think things get "over-EIP'ed" many times. In general I just try and keep routes as short as humanly possible, as asynchronous as possible and as distributable as possible. Whenever I

Re: [DISCUSS] Move to a pure git based repo

Cloned nicely. (And danged fast). On May 6, 2013, at 7:45 AM, Christian Müller wrote: > The Git repository looks good to me too (master, branches, tags). > > I tried to update our CI builds to use our new Git repository, but I got an > exception. There is also no explanation at https://git-wip

Re: [VOTE] Release Apache Camel 2.11.0 (take 4)

+1 On Apr 18, 2013, at 11:28 AM, Scott England-Sullivan wrote: > +1 > > > On Thu, Apr 18, 2013 at 3:57 AM, Charles Moulliard wrote: > >> +1 >> >> >> On Wed, Apr 17, 2013 at 10:11 PM, Christian Müller < >> christian.muel...@gmail.com> wrote: >> >>> After 9 month of development, we have a

Re: IDEA 12.1 cannot build Apache Camel project anymore

I'll look. You normally just point to the parent Pom and say open project. If generated sources for test are missing for a module you can easily add that. On Apr 8, 2013, at 14:08, Daniel Kulp wrote: > > On Apr 8, 2013, at 3:05 PM, Babak Vahdat wrote: > >> I do exactly the same SIMPLE way th

Re: Commercial Camel Offerings page

Here I thought Camel was an Apache Project - didn't know it was part of RedHat On Mar 2, 2013, at 2:52 AM, Charles Moulliard wrote: > Hi Maciek, > > As Camel framework is now part of the RedHat Middleware portfolio, I would > like to know if you could be interested to become a RedHat par

Re: Contributing Scomp Component (was Contributing Stomp Component)

I have to say I kinda agree with this. We could mark a component as possibly "less quickly patched", but nixing contributions on a component level seems kinda wrong to me... On Feb 7, 2013, at 1:20 PM, Henryk Konsek wrote: >> Because Camel and Camel-Extra are Java based projects, I don't think

Re: [DISCUSS][CAMEL-3.0] Does camel need a web console

Either or, I prefer 2 but sandbox might be a good idea. On Jan 25, 2013, at 16:43, Hadrian Zbarcea wrote: > I'd keep this thread short and focus on achieving consensus (if possible) on > what to do with the existing console. So far it looks to me like there is > (almost(*)) consensus on not ha

Re: [VOTE] Release Apache Camel 2.10.3

+1 On Dec 4, 2012, at 5:36 AM, Claus Ibsen wrote: > +1 > > On Mon, Dec 3, 2012 at 4:06 AM, Hadrian Zbarcea wrote: >> A new patch release candidate apache-camel-2.10.3 final is out with >> approximately 74 issues resolved so far: improvements and bug fixes [1]. >> >> Please find the staging rep

Re: [VOTE] Release Apache Camel 2.9.5

+1 On Dec 2, 2012, at 15:01, Christian Müller wrote: > +1 > I run the Camel in Action test suite (rev 337). All unless the XA tests > passed (known issue - also in previous releases). > > Best, > Christian > > On Thu, Nov 29, 2012 at 7:33 PM, Hadrian Zbarcea wrote: > >> new patch release can

Re: [HEADS UP] - Camel trunk has been upgraded to Aries 1.0.0 / OSGi 4.3.0 / Karaf 2.3.0

Looks like a bad export similar to this... https://fisheye6.atlassian.com/browse/servicemix/smx4/features/branches/features-4.4.x/assemblies/shared/src/main/resources/etc/custom.properties?r2=1359361&r1=1226814 On Nov 5, 2012, at 7:13 AM, Claus Ibsen wrote: > Hi > > Its been a challenge to upgr

Re: [VOTE] Release Apache Camel 2.10.2

+1 On Oct 11, 2012, at 11:43 AM, Hadrian Zbarcea wrote: > A new patch release candidate apache-camel-2.9.4 final is out with > approximately 71 issues resolved so far: improvements and bug fixes [1]. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/or

Re: ZeroMQ contribution - Any thoughts on licensing hack

+1 to extras. It is a murky area since it sure, is generated code... On Sep 25, 2012, at 10:08 AM, James Carman wrote: > Agreed (as I pointed out on the JIRA). > > On Tue, Sep 25, 2012 at 11:43 AM, Daniel Kulp wrote: >> >> I would personally just suggest Camel extras and be done with it.

Re: [VOTE] Apache Camel 2.9.3 and 2.10.1

+1 Tested with Karaf and CXF On Aug 28, 2012, at 1:56 AM, Aki Yoshida wrote: > +1 (non-binding) > > tested 2.10.1 with cxf 2.6.2 setup. > > 2012/8/24 Daniel Kulp : >> >> It's been quite a while since 2.9.2. We're long overdue for 2.9.3. It's >> also a good time for 2.10.1. >> >> We've fix

Re: [VOTE] Apache Camel 2.9.3 and 2.10.1

+1 We need to get this out. On Aug 27, 2012, at 11:18 PM, Claus Ibsen wrote: > +1 > > The PDF manual hasn't been updated to 2012 in its date range > Copyright 2007-2011, Apache Software Foundation > > > > On Fri, Aug 24, 2012 at 7:04 PM, Daniel Kulp wrote: >> >> It's been quite a while sin

Re: fyi - SI

But is it better? On Jul 15, 2012, at 4:36 PM, Christian Müller wrote: > Thanks Adam for this pointer. > I respond to this thread with an optimized version of the Camel route which > is about two times faster than the Spring integration solution. > > Best, > Christian > > On Sun, Jul 15, 201

Re: [CAMEL-5416] Camel Simple JMS Component

Also, are we paying attention to pool reusage in a container? Another dumb question ;) On Jul 9, 2012, at 21:53, Scott England-Sullivan wrote: > Christian, > > I am looking into creating a new Apache Commons project for the messaging. > As information becomes available I will let you know. >

Re: [DISCUSS] force switching from SVN to GIT

I'd be +1 for the offline, branching and commit simplicity as well as a easier merge. On Jul 9, 2012, at 22:35, Daniel Kulp wrote: > On Monday, July 09, 2012 09:48:32 PM Christian Müller wrote: >> I would like to get your opinion about switching from SVN to Git [1]. >> At this point Git suppor

Re: [CAMEL-5416] Camel Simple JMS Component

Is there any reason for not using commons pool then? Just a stupid question. On Jul 9, 2012, at 21:53, Scott England-Sullivan wrote: > Christian, > > I am looking into creating a new Apache Commons project for the messaging. > As information becomes available I will let you know. > > On Thu,

Re: [VOTE] Release Apache Camel 2.10.0 (2nd attempt)

+1 On Jun 28, 2012, at 15:47, Christian Schneider wrote: > +1 > > Christian > > Am 28.06.2012 04:39, schrieb Hadrian Zbarcea: >> A new release candidate apache-camel-2.10.0 final is out with approximately >> 483 issues resolved so far: improvements and bug fixes [1]. >> >> Please find the st

Re: [VOTE] Release Apache Camel 2.10.0 (2nd attempt)

+1 On Jun 28, 2012, at 7:46 AM, Ashwin Karpe wrote: > +1 > > - > - > Ashwin Karpe > Apache Camel Committer & Sr Principal Consultant > FUSESource (a Progress Software Corporation subsidiary) > http://fusesource.com > > Blog: http://op

Re: [VOTE] Release Apache Camel 2.10.0

+1 On Jun 22, 2012, at 3:51 PM, Christian Müller wrote: > +1 > > My tests/findings: > > 1) all new components are in the kit > 2) I could not install camel-dns in Karaf 2.2.7 (see below) > -> package sun.net.spi.nameservice is neither exported by Karaf nor > provided by another bundle > 3) I

Re: [DISCUSS] - Camel 2.9.3 Release

+1 On Jun 20, 2012, at 12:45, Hadrian Zbarcea wrote: > Absolutely :) > Hadrian > > On 06/20/2012 02:37 PM, Christian Müller wrote: >> +1 >> And don't forget the 2.8.x branch ;-) >> Because we have decided to support (at least) the last two release >> branches, we should cut a 2.8.x version as w

Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints

+1, WIth the fact that converters exist, we aren't breaking anything in 2 /je On Jun 20, 2012, at 10:29 AM, Hadrian Zbarcea wrote: > +1 > Hadrian > > On 06/19/2012 08:37 PM, Hadrian Zbarcea wrote: >> Using URIs to identify and configure Endpoints is a notable Apache Camel >> innovation. This fe

Re: [DISCUSS] - camel-websocket component

+1 On Jun 12, 2012, at 3:56 PM, Christian Müller wrote: > +1 from my point of view. > > Christian > > Sent from a mobile device > Am 11.06.2012 18:52 schrieb "Daniel Kulp" : > >> >> This does make a lot of sense to me. websocket is really a standard for >> which there could be multiple imp

Re: [DISCUSS] - Apache Camel 2.10 release

+1, would be less confusing. On Jun 2, 2012, at 12:18 PM, David Karlsen wrote: > +1 to that. > > 2012/6/2 Daniel Kulp : >> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote: >>> Hi >>> >>> So the Java 7 support is now done. >>> And when CXF 2.6.1 is out, we should be in a shape for a rel

Re: [jira] [Created] (CAMEL-5321) Validator Component Fails on XSD with Classpath Relative Imports

Good catch. On May 30, 2012, at 5:56 PM, Scott England-Sullivan (JIRA) wrote: > Scott England-Sullivan created CAMEL-5321: > - > > Summary: Validator Component Fails on XSD with Classpath Relative > Imports > Key: CAMEL-532

Re: svn commit: r1336571 - /camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/DefaultCxfBinding.java

We don't make claims from a Camel side. CXF makes the claims on that, if we can adhere to a range, we certainly I think should do so in an integration framework. Deciding what others could / should do when there is opportunity for choice tends to be the wrong way in my humble opinion. /je On M

Re: Split XML file

You want an enumeration of Persons On May 9, 2012, at 9:52, alexis229 wrote: > Hi guys! > > First of all, I'm a beginner in apache camel, I try to develop a very basic > route which split a XML file (see below). > > * > James > John > Strachan > London > * > > > My goal is to have, in

Re: [VOTE] Release Apache Camel 2.8.5

+1 On Apr 25, 2012, at 1:46 AM, Rob Davies wrote: > +1 > On 23 Apr 2012, at 21:14, Hadrian Zbarcea wrote: > >> A new patch release candidate apache-camel-2.8.5 is out with approximately >> 46 issues resolved: improvements and bug fixes [1]. >> >> Please find the staging repo here: >> https://

Re: [VOTE] Release Apache Camel 2.9.2

+1 On Apr 13, 2012, at 7:53, Jean-Baptiste Onofré wrote: > +1 > > Tested in Karaf 2.2.6 and 2.2.5 > > Regards > JB > > On 04/12/2012 03:44 PM, Hadrian Zbarcea wrote: >> A new patch release candidate apache-camel-2.9.2 is out with >> approximately 57 issues resolved so far: improvements and bu

Re: Remove Camel HTTP component in Camel 3.0?

+1 On Apr 9, 2012, at 10:05 AM, Hadrian Zbarcea wrote: > +1. I wanted to say the same thing. Dan beat me to it. > Hadrian > > On 04/09/2012 12:02 PM, Daniel Kulp wrote: >> On Monday, April 09, 2012 05:43:15 PM Claus Ibsen wrote: >>> Its just that Apache iBatis moved out of Apache, and is no longe

Re: [jira] [Commented] (CAMEL-3776) Add pooling support for JAXB data format

I have implemented this for other things, you really need to pool the marshallers/unmarshallers in an Object Pool or something similar. One way was to override and extend / override the whole context. On Apr 2, 2012, at 3:07 PM, Christian Müller (Commented) (JIRA) wrote: > >[ > https://i

Re: [DISCUSS] Camel Alerts

Well, a user designed OID is a derivative of a MIB, that is what tells you what is what. And there are the two sides to snmp, alerting events and the polling monitoring side. So if you look at a router say, CPU/Memory are predefined OID's in a system mib, then you have interfaces x.25, frame re

Re: svn commit: r1296787 - in /camel/trunk/camel-core/src: main/java/org/apache/camel/processor/UnmarshalProcessor.java main/java/org/apache/camel/spi/DataFormat.java test/java/org/apache/camel/proces

Thank you Babak! On Mar 5, 2012, at 1:15 AM, Babak Vahdat wrote: > Hi Claus > > I did relax that notNull restriction now. > > Babak > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Re-svn-commit-r1296787-in-camel-trunk-camel-core-src-main-java-org-apache-camel-proces

Re: svn commit: r1296787 - in /camel/trunk/camel-core/src: main/java/org/apache/camel/processor/UnmarshalProcessor.java main/java/org/apache/camel/spi/DataFormat.java test/java/org/apache/camel/proces

Eeee…. We can't just change API :) On Mar 5, 2012, at 12:51 AM, Claus Ibsen wrote: > Hi Babak > > It should be okay for the unmarshal processor to return null, which > means the body should be set to null as a result. > You have introduced a not null check, which now will cause problems. > >

Re: [VOTE] Release Apache Camel 2.9.1

+1 On Mar 4, 2012, at 7:26 AM, Babak Vahdat wrote: > +1 > > Babak > > -- > View this message in context: > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-9-1-tp5528628p5535304.html > Sent from the Camel Development mailing list archive at Nabble.com.

Re: [DISCUSS] Camel Alerts

I actually think SNMP would be more than enough. The problem resides in designing a MIB. One of the biggest culprits of Java is JMX, while great it isn't that "greatly and happily" adopted, combining snmp traps with snap OID reads (Which JMX set out to do) would provide a ton of info not to men

Re: [DISCUSS] Camel Alerts

+1, I like the proposal, well-written nice ideas. I also appreciate the fact that you acknowledge that the spring batch integration would not be sufficient work. I'm sure there are several that would want to help, sometimes splitting up the mentoring work a little bit isn't a bad idea, somethin

Re: [jira] [Created] (CXF-4084) Blueprint http

1:16:20 PM Aki Yoshida wrote: >>> Hi Dan, >>> I can look into this item using a similar approach used in ws-rm using >>> the merged schemas. >>> Let me know if you see some issues. >> >> Just make sure you work with Johan Edstrom. I think

Re: [VOTE] Release Apache Camel 2.8.4

+1 On Jan 27, 2012, at 12:09 PM, Jon Anstey wrote: > Looks good to me. Very nice to see a beautiful PDF user guide in this one > too :) > > +1 > > On Wed, Jan 25, 2012 at 9:54 AM, Hadrian Zbarcea wrote: > >> A new patch release candidate apache-camel-2.8.4 is out with approximately >> 88 issu

Re: [VOTE] Release Apache Camel 2.8.4

+1 On Jan 25, 2012, at 6:42 AM, Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB > > On 01/25/2012 02:24 PM, Hadrian Zbarcea wrote: >> A new patch release candidate apache-camel-2.8.4 is out with >> approximately 88 issues resolved: improvements and bug fixes [1]. >> >> Please

Re: [DISCUSS] - About the setup.eclipse Profile we have

Eclipse? :) +1 - sure. On Jan 18, 2012, at 12:45 AM, Jean-Baptiste Onofré wrote: > Hi Babak, > > to be honest I don't care as I don't use Eclipse ;) > So you have my +1 > > Regards > JB > > On 01/17/2012 05:19 PM, Babak Vahdat wrote: >> Hi, >> >> couple of weeks ago I had a long mail convers

Re: [jira] [Issue Comment Edited] (CAMEL-4796) Code Clean-Up

Babak! Pretty awesome cleanup, thanks from all of us! /je On Jan 14, 2012, at 8:38 PM, Babak Vahdat (Issue Comment Edited) (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/CAMEL-4796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186393#

Re: [DISCUSS] Dropping support for Camel 2.7.x

+1 On Dec 31, 2011, at 23:59, "j...@nanthrax.net" wrote: > +1 > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://wwx.talend.com > > - Reply message - > From: "Christian Müller" > To: "dev@camel.apache.org" > Subject: [DISCUSS] Dropping su

Re: Whats about a camel-all feature

I think that'll be a whole lotta work for something you can do in awk or perl in about 2 seconds…. Just my .2 On Dec 29, 2011, at 3:25 PM, Christian Müller wrote: > What do you think about a "camel-all" features which installs all available > Camel features with one command? This make it more e

Re: [DISCUSS] - Remove Camel 1.x only material from the wiki documentation

+1 On Dec 29, 2011, at 3:54 AM, Jean-Baptiste Onofré wrote: > +1 > > Fully agree, > > Regards > JB > > On 12/29/2011 10:22 AM, Claus Ibsen wrote: >> Hi >> >> Camel 1.x has been EOL for about 1 year now >> http://camel.apache.org/2010/12/17/camel-164-released.html >> >> In our wiki documentat

Re: [VOTE] Release Apache Camel 2.9.0

Built and deployed with karaf and some custom tests +1 On Dec 29, 2011, at 7:18 AM, Claus Ibsen wrote: > Gave it a test run with the Camel in Action source code. > > +1 > > On Wed, Dec 28, 2011 at 4:36 AM, Hadrian Zbarcea wrote: >> A new release candidate apache-camel-2.9.0 final is out wit

Re: [PROPOSAL] - camel-test - @deprecate JUnit 3.x API

+1, I like that. On Dec 28, 2011, at 8:08 AM, Claus Ibsen wrote: > Hi > > The camel-test component supports currently both JUnit 3.x and 4.x, > each in separate package. > Supporting both requires us to have a fair amount of duplicated code, > one for 3.x and another for 4.x. > > I suggest to @

Re: [CANCEL][VOTE] Release Apache Camel 2.9.0

My .2 is that I haven't really used this stack commercially ever without at least some of the CXF features, I know that cxf is large, sure but since the cxf defaults when setup right provides better than jre settings for quite a few things, faster stax parsing etc etc. I kinda sorta wanna see

Re: [VOTE] Release Apache Camel 2.9.0

Having done the same tests +1 And a great Holiday and all that good stuff to all of you! On Dec 21, 2011, at 3:58 PM, Christian Müller wrote: > Yeah, let's see what the other guys think... > Because we could solve these issues be installing the needed > features/bundles first, I think they are

Re: [jira] [Commented] (CAMEL-4811) camel-ognl featues doesn't work

Wrong dep version, http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.javassist/3.11.0.GA_2/ Needs this one…. On Dec 21, 2011, at 3:03 PM, Christian Müller (Commented) (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/CAMEL-4811?page=com.at

Re: [VOTE] Release Apache Camel 2.9.0

Sorry for this going offline dev for a few iterations, most of the deployment errors noted on dev for 2.9.0 was due to not having the cxf feature loaded early. Since I posted this to you directly - maybe we should ask all the other CXF guys? Servciemix will pull in the CXF-Bundle giving us pre

Re: [VOTE] Release Apache Camel 2.9.0

Yep, missing karaf feature eventadmin…. On Dec 21, 2011, at 11:03 AM, Christian Müller wrote: > We also have an issue to install camel-eventadmin: > > Christian-Muellers-MacBook-Pro:bin cmueller$ ./karaf clean > > karaf@root> features:addurl > mvn:org.apache.camel.karaf/apache-camel/2.9.0/xml/

Re: [VOTE] Release Apache Camel 2.9.0

How are you deploying this - clean karaf 2.2.4? I just did the same in karaf 2.2.4 and camel copied from the 2.9.0 staging tars, That export should be coming from a system bundle, servicemix-stax Apache ServiceMix :: Specs :: Stax API 1.0 (128) M

Re: [VOTE] Release Apache Camel 2.9.0

+1 On Dec 15, 2011, at 11:41 PM, Jean-Baptiste Onofré wrote: > +1 (non binding) > > Tested in Karaf with a set of example, mostly in blueprint. > I installed all camel features with changes (the ones which use jetty/war > feature in place of the geronimo-servlet, geronimo-jsp, geronimo-el bund

Re: [DISCUSS] - Align Camel karaf commands as Karaf is doing

+1 On Dec 5, 2011, at 1:50 AM, Christian Müller wrote: > +1 > > Sent from a mobile device > Am 02.12.2011 16:30 schrieb "Claus Ibsen" : > >> Hi >> >> On the Karaf @dev they are talking about changing the naming of the >> commands. >> >> http://karaf.922171.n3.nabble.com/PROPOSAL-New-Karaf-com

Re: syslog RFC 5424 dataformat component

I'll just need to get past the Turkey hibernation :) But it would be awesome I think if we could remain in the ASF license land with one component, checking for which converter to use in the converters and specifying manually one of the two in a declared context? That make sense? So we'd need an

Re: syslog RFC 5424 dataformat component

It doesn't look from just reading the RFC as if it would be that hard to distinguish Between : <34>Oct 11 22:14:15 mymachine su: 'su root' failed for lonvick on /dev/pts/8 <34>1 2003-10-11T22:14:15.003Z mymachine.example.com su - ID47 - BOM'su root' failed for lonvick on /dev/pts/8 The latte

Re: syslog RFC 5424 dataformat component

I'd be nice if we could just handle both. I'm game if you want to chat about it, the first one I just wrote to get a basic setup, the whole syslog world suffers from not being that greatly standardized :) /je On Nov 23, 2011, at 7:09 AM, geemang wrote: > The spec does not say anything about bac

Re: [RESULT][VOTE] Release Apache Camel 2.9.0-RC1

I just managed to get to testing A very late +1, how about the "Changes" notice that Dan and I were working on? I really just wanted to communicate, yes this release we had more changes than anticipated, hence the update on what was going on, we also have some really nice stuff in the patch br

Re: New mina2 component test fails with "No component found with scheme: mina2"

Do you have all of the auto discovery files there correctly? http://camel.apache.org/writing-components.html /je On Oct 30, 2011, at 1:10 PM, Chad Beaulac wrote: > I'm working on a mina2 component. Unit tests that use the Java DSL pass. > Unit tests that use the TemplateProducer fail with an er

Re: [VOTE] Release Camel 2.8.2

+1. Contacted Richard to resolve that. On Oct 18, 2011, at 11:49 PM, Claus Ibsen wrote: > Hi > > Just a minor observation > > The patch from which was backported to 2.8.2 > https://issues.apache.org/jira/browse/CAMEL-4558 > > Was not granted license to Apache. I have asked the contributor to

Re: [VOTE] Release Camel 2.7.4

+1 on this. Thanks! On Oct 18, 2011, at 11:01 PM, Christian Schneider wrote: > +1 > > Christian > > Am 17.10.2011 23:12, schrieb Daniel Kulp: >> This is a vote to release Camel 2.7.4. 2.7.4 contains fixes for over 11 JIRA >> issues that would be good to get into the hands of Camel users. >> >

Re: Features

gt;> first looking if there's a feature descriptor installed that matches the >> version range and only then trying to resolve and install it? >> >> Regards, >> >> Gert Vanthienen >> >> FuseSource >> Web: http://fusesour

Re: [VOTE] Release Camel 2.8.2

Good catch, thanks! On Oct 18, 2011, at 11:49 PM, Claus Ibsen wrote: > Hi > > Just a minor observation > > The patch from which was backported to 2.8.2 > https://issues.apache.org/jira/browse/CAMEL-4558 > > Was not granted license to Apache. I have asked the contributor to > re-submit the patc

Re: Features

tes if possible. > > On Saturday, October 15, 2011, Johan Edstrom wrote: >> Yup, >> >> I probably had spent another few days without that previous knowledge, it > is still >> in need of work. >> >> And using the OBR given the complexity I think personall

Re: Features

natype OBR repo last week, that would help. /je On Oct 15, 2011, at 12:26 AM, Daniel Kulp wrote: > On Friday, October 14, 2011 11:58:26 PM Johan Edstrom wrote: >> Hey, >> >> Just poking around in the features, and yes I cross post this - >> >> I know there has

Features

Hey, Just poking around in the features, and yes I cross post this - I know there has been work going on with regards to creating a sane default set of features but currently the CXF features in 2.4.2 (I think it was) uses spring 3.0.6, the karaf features 3.0.5 and the camel features actually

Re: Camel 2.8.2 - Reason for the many backports?

I'll step in here… Much of what Dan has done is in the corporate world very very much wanted. Dan offered his time to keep on back porting fixing and non api breaking features. That means we'll see (and we can debate that) "done in 2.9, available in 2.8.5) I think Dan already said he should hav

Re: [VOTE] Release Apache Camel 2.8.1

+1 On Sep 8, 2011, at 2:29, Freeman Fang wrote: > Hi, > > Build servicemix-camel JBI component and smx4 kit against Camel 2.8.1, and > all camel related example there works well. > Here is my +1 > > Freeman > On 2011-9-7, at 上午3:27, Zbarcea Hadrian wrote: > >> A new patch release apache-cam

Re: [DISCUSS] - API stability in Camel 2.x

With deprecate changes, we'll have no issues at all, so there I do not see it as a "change" at all. /je On Sep 5, 2011, at 9:16 AM, Zbarcea Hadrian wrote: > Claus, > > How exactly did you get to figure out what the community wants "NO CHANGES" > in the the API an via what process were you nomi

Re: What is the purpose of camel-core-xml? Move the code to camel-core?

SInce I work pretty much 97.98% in osgi, I'll weigh in and say that I really like this. If XML is only used from Blueprint / Spring-DM, we provide those with the features descriptors, they import nothing - i.e. are model/api bundles, why make a jar bigger? I really don't think we should refactor c

Re: [jira] [Commented] (CAMEL-4371) Add an ability to replace endpoints

If you are doing this in service mix, there is a far easier and much more dynamic way of doing this. What you do is a factory service, this you can write an interface via constructors for in tests, if you after that basically have the same structure/route but different locations and say CXF stra

Re: camel-core - Checkstyle issues on trunk

Would a tag+IDE cleanup be something acceptable? I have camel check style profiles I use, I've noticed they can differ a tiny bit from the eclipse one and still pass, but do we simply need one strict enforcement and then we stay more critical to the issue? Just a wild IDEa… :) /je On Aug 27, 2

Re: [DISCUSS] - Apache Camel 2.8.1 release

Very interested in getting both camel 2.8.x and amq 5.6 in SMX, so yes +1. On Aug 25, 2011, at 5:59 AM, Hadrian Zbarcea wrote: > +1 > > > On 08/25/2011 03:58 AM, Claus Ibsen wrote: >> Hi >> >> Its been 1 month since Camel 2.8.0 was released. >> And we have a 2.8 branch where we have merged bug

Re: Need Urgent Help

Please use the users list for questions on how to use Camel. Also there is plenty of documentation on http://camel.apache.org/ /je On Fri, Aug 19, 2011 at 7:32 AM, khinvra wrote: > Hi all, > we need urgent help in... > > 1) sample code for publishing data/xml through camel-java-servicemix to an

Re: [jira] [Updated] (CAMEL-4345) Synchronized code causes long delays and hangs for big applications especially with Blueprint

Very unscientifically testing this a 200 route count with 20 prepped exchanges went from 20 secs to 8 seconds, more interestingly though a 400 route count with 500 exchanges each that previously caused either a hang or a oome now takes around 40 seconds with the majority of time spent on route b

Re: [DISCUSS] - Adjust Apache Camel product descriptions

We could even say "we are not spring based, as we are focused on providing an integration library that will co-exist in pretty much any container, deployment environment as well. /je On Aug 14, 2011, at 8:12 PM, Willem Jiang wrote: > +1 to remove the descriptions of the Spring based. > > On

Re: [DISCUSS] - Dropping Maven 2.x support

+1, sounds like one less thing to worry about. /je

  1   2   >