Re: [RESULT][VOTE] Release Apache Camel 2.10.3
Hi Seems the release never got announced or the last bits of the release process done. The new 2.10.3 and 2.9.5 releases are distributed to - Maven Central - Apache Mirror Download sites So its a matter of getting these release announced and update the online XSD schema files. And follow the release guide at: http://camel.apache.org/release-guide.html It seems Hadrian dont have the time to do this, or do not prioritize to do so. Any other takes to get these release out of the door to the community? On Thu, Dec 6, 2012 at 6:38 PM, Claus Ibsen wrote: > Hi Hadrian > > Do you mind update the XSD as well so we have them all online? > I think we got a JIRA ticket about the previous released didn't have > their XSD published. > > And if you are harvesting for beers. Then updating the javadoc would be cool. > Its currently from the 2.9.0 release. > > > > On Thu, Dec 6, 2012 at 1:37 PM, Hadrian Zbarcea wrote: >> The vote passes with: >> >> [9] +1 (hadrian, cibsen, joed, dkulp, ningjian, cschneider, cmueller, >> bvahdat, janstey) >> [1] +1 (non-binding) >> [0] -1 >> >> I will finish publishing the artifacts and make the announcement (for both >> this and 2.9.5 released earlier this week) after everything is pushed pushed >> to the mirrors. >> >> Thanks to all who tested this release and voted. >> Hadrian >> >> >> On 12/02/2012 10:06 PM, 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 repo here: >>> https://repository.apache.org/content/repositories/orgapachecamel-107/ >>> >>> The tarballs are here >>> >>> https://repository.apache.org/content/repositories/orgapachecamel-107/org/apache/camel/apache-camel/2.10.3/ >>> >>> >>> Tag: >>> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.3/ >>> >>> Please review, help out with testing and vote to approve this release >>> binary. Your vote counts! >>> >>> [ ] +1 Release the binary as Apache Camel 2.10.3 >>> [ ] -1 Veto the release (provide specific comments) >>> Vote is open for at least 72 hours. >>> >>> Here's my +1. >>> Hadrian >>> >>> [1] >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12323366 >>> >>> >>> >> > > > > -- > Claus Ibsen > - > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
How to have more than one condition in simple expression language
Hi,
I have a choice block in a camel route similar to :-
${header.myProp} == 'myTestProp' && ${body} contains
'stringToFind'
However, I get a compilation error:-
The entity name must immediately follow the '&' in the entity reference.
I'm using Camel 2.9 so as far as I can see the 'and' and 'or' operators are
deprecated. Would appreciate it if someone could reply with a way around
this. I've tried a few different approaches, some that compile but seem to
produce unexpected results.
Regards,
Justin
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-have-more-than-one-condition-in-simple-expression-language-tp5723898.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: How to have more than one condition in simple expression language
Hi Justin, try using the word "and" instead of && Bilgin On 11 December 2012 11:34, justinblandford wrote: > The entity name must immediately follow the '&' in the entity reference.
Re: Apach Camel
Please use the users@ mailing list for such kind of questions. What did you try so faw and struggeling with? Best, Christian Sent from a mobile device Am 11.12.2012 04:38 schrieb "Sam Amor" : > > Dear Sir or Madam, > can you help me with my exercise in Apach Camel > Thanks in Advance > i have the following tasks to do : > - Aggregate information (See Minimum 7 book information. Including title, > description, author, cover, page number, ISBNs, similar books, price, > release date)- Via SQS refer to another Camel instance- Save in the second > Camel instance via S3- Make information in the second Camel instance > available in an RSS feed via HTTP > > i know that are so many tasks, but i dont know how to handle them.thanks > in advances > Sam > > >
Re: How to have more than one condition in simple expression language
ohh, also the user list is better place for these kind of questions. This list is for developing Apache Camel itself HTH Bilgin On 11 December 2012 12:57, Bilgin Ibryam wrote: > Hi Justin, > > try using the word "and" instead of && > > Bilgin > > On 11 December 2012 11:34, justinblandford > wrote: >> The entity name must immediately follow the '&' in the entity reference.
Re: Fwd: ASF Board Report for Dec 2012 is now due
I would just take out the 2 lines about Camel in the news, not really relevant for the board. Other than that, it looks good. My $0.02, Hadrian On 12/10/2012 03:06 PM, Christian Mueller wrote: I plan to submit our Dec 2012 Apache Camel board report at 12 December 2012 (in 2 days). You can find the draft version at [1]. Please feel free to comment it. Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns. Project Status -- * There are no issues that require the board attention. * The project is healthy, active and stays at a high level. Community - * Apache Camel in the news: * "Java aktuell - Das Magazin" and "Java Spektrum" published articles about Apache Camel. * At ApacheCon EU 2012 we had 4 talks about Apache Camel. * The community stays at a high level (183 subscribers at dev@; 503 subscribers at users@) * The community is active and questions being answered in short term. * Avg. 795 mails per month on the users mailing list in Sep 2011 - Nov 2012 * Avg. 247 mails per month on the dev mailing list in Sep 2011 - Nov 2012 * Avg. 402 committs per month in Sep 2011 - Nov 2012 * We welcome Henryk Konsek, Raul Kripalani and Scott England-Sullivan as new committer. * We welcome Babak Vahdat and Charles Moulliard in our PMC. * After acquiring FuseSource by RedHad and inviting two committers, our PMC of 21 is affiliated with 7 different unique organizations (13 of them are affiliated with a single company). * Our additional 17 committers belongs to 14 different unique organizations (4 of them are affiliated with the same single company mentioned above). Community Objectives * Finalizing our working on Camel 2.11.0 * Plan the work for Camel 3.0.0 Releases * 2.9.4 * 2.9.5 * 2.10.2 * 2.10.3 [1] https://cwiki.apache.org/confluence/display/CAMEL/Status+report+for+the+Apache+Camel+project+-+December+2012+-+work+in+progress Best, Christian -- Forwarded message -- From: ASF Board Date: Sun, Dec 9, 2012 at 6:41 PM Subject: ASF Board Report for Dec 2012 is now due To: Christian Mueller This email was sent by an automated system on behalf of the ASF Board. According to board records, you are listed as the chair of at least one committee that is due to submit a report this month. These reports are now due and should be submitted to the board as soon as possible but no later that Wed, Dec 12th. The meeting is scheduled for Wed, 19 December 2012, 10:00:00 PST. Full details about the process and schedule are in [1]. The report should be committed to the meeting agenda in the board directory in the foundation repository, trying to keep a similar format to the others. This can be found at: https://svn.apache.org/repos/private/foundation/board Your report should also be sent in plain-text format to bo...@apache.org with a Subject line that follows the below format: Subject: [REPORT] Project Name Cutting and pasting directly from a Wiki is not acceptable due to formatting issues. Line lengths should be limited to 77 characters. As always, PMC chairs are welcome to attend the board meeting. Thanks, The ASF Board [1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt [2] - https://svn.apache.org/repos/private/committers/board/templates Resolutions --- There are several templates for use for various Board resolutions. They can be found in [2] and you are encouraged to use them. It is strongly recommended that if you have a resolution before the board, you are encouraged to attend that board meeting. ASF Board Reports - Reports are due from you for the following committees: - Camel
Re: JMapper Framework
Hi Alessandro Thanks for sharing this with us. I assume you use some byte code manipulation to have the performance of the static code? On Mon, Dec 10, 2012 at 2:30 PM, Alessandro Vurro wrote: > Hello Camel team, > > I noticed that you used dozer to perform conversions, the problem of Dozer > is performance. A static mapping of the duration of one millisecond with > Dozer takes approximately one second. > > I wanted to bring to your attention a new framework "JMapper" that allows > you to perform dynamic mappings with annotations and / or XML bringing > several advantages as: > - create and enrich target objects > - apply specific logic to the mapping (only valued fields, null fields > only, etc. ..) > - automated management of the XML file > - Possibility of Implementing the 1 to N and N to 1 relationships > - explicit conversions > > JMapper permits to have all advantages of dynamic mapping with the > performance of static code. > > http://code.google.com/p/jmapper-framework/ > > thank you for your attention -- Claus Ibsen - Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: property-placeholder + OSGI
Camel 2.10. and before is tested with Karaf 2.2.x as you can read here: http://camel.apache.org/karaf.html Camel 2.11 will be the first version officially supporting Karaf 2.3.x. Best, Christian On Tue, Dec 11, 2012 at 8:43 AM, SpinWin wrote: > Hi, > > To answer your questions : > > Karaf version : 2.3.0 > > And the NPE Stack Trace : > > org.osgi.service.blueprint.container.ComponentDefinitionException: > java.lang.NullPointerException > at > > org.apache.aries.blueprint.container.ReferenceRecipe.internalCreate(ReferenceRecipe.java:116)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[7:org.apache.aries.blueprint.core:1.0.1] > at > > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_27] > at > java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_27] > at > > org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BeanRecipe.setProperty(BeanRecipe.java:933)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:907)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BeanRecipe.setProperties(BeanRecipe.java:888)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:820)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[7:org.apache.aries.blueprint.core:1.0.1] > at > > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_27] > at > java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_27] > at > > org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintRepository.createInstance(BlueprintRepository.java:230)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintRepository.create(BlueprintRepository.java:155)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintContainerImpl.processProcessors(BlueprintContainerImpl.java:496)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:338)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:252)[7:org.apache.aries.blueprint.core:1.0.1] > at > > org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[7:org.apache.aries.blueprint.core:1.0.1] > at > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_27] > at > > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)[:1.6.0_27] > at > java.util.concurrent.FutureTask.run(FutureTask.java:138)[:1.6.0_27] > at > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)[:1.6.0_27] > at > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)[:1.6.0_27] > at > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_27] > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_27] > at java.lang.Thread.run(Thread.java:662)[:1.6.0_27] > Caused by: java.lang.NullPointerException > at > > org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1432) > at > > org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72) > at > > org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843) > at java.lang.ClassLoader.loadClass(ClassLoader.java:295)[:1.6.0_27] > at java.lang.ClassLoader.loadClass(ClassLoader.java:247)[:1.6.0_27] > at java.lang.Class.forName0(Native Method)[:1.6.0_27] > at java.lang.Class.forName(Class.java:247)[:1.6.0_27] > at > > org.apache.aries.proxy.impl.interfaces.ProxyClassLoader.isInvalid(ProxyClassLoader.java:109)[12:org.apache.aries.proxy.impl:1.0.0] > at > > org.apache.aries.pr
Re: [RESULT][VOTE] Release Apache Camel 2.10.3
Unfortunately I'm more than busy with other tasks... If Hadrian (in CC) doesn't respond until tomorrow, we will find one... But I'm sure he will respond... Best, Christian On Tue, Dec 11, 2012 at 9:11 AM, Claus Ibsen wrote: > release
Re: svn commit: r1420455 - /camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
Hi Christian，
This change breaks some unit tests of camel-core, can you have a look at them ?
BTW,
wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@301a69c]
is really a good trace lab for us to use.
Failed tests:
testOk(org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest):
expected:<[ref:myProcessor]> but
was:<[wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@301a69c]]>
testWithError(org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest):
expected:<[ref:myProcessor]> but
was:<[wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@10042865]]>
testSynchronizeComplete(org.apache.camel.processor.OnCompletionGlobalTraceTest):
expected:<[ref:myProcessor]> but
was:<[wrap[org.apache.camel.processor.OnCompletionGlobalTraceTest$MyProcessor@4f4c55e7]]>
testSynchronizeFailure(org.apache.camel.processor.OnCompletionGlobalTraceTest):
expected:<[ref:myProcessor]> but
was:<[wrap[org.apache.camel.processor.OnCompletionGlobalTraceTest$MyProcessor@256949fd]]>
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | 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: 姜宁willem
On Wednesday, December 12, 2012 at 6:06 AM, cmuel...@apache.org
(mailto:cmuel...@apache.org) wrote:
> Author: cmueller
> Date: Tue Dec 11 22:06:32 2012
> New Revision: 1420455
>
> URL: http://svn.apache.org/viewvc?rev=1420455&view=rev
> Log:
> CAMEL-5844: Camel Tracer not showing some EIP names
>
> Modified:
> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
>
> Modified:
> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
> URL:
> http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java?rev=1420455&r1=1420454&r2=1420455&view=diff
> ==
> ---
> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
> (original)
> +++
> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
> Tue Dec 11 22:06:32 2012
> @@ -19,14 +19,14 @@ package org.apache.camel.processor;
> import java.util.List;
>
> import org.apache.camel.Processor;
> +import org.apache.camel.Traceable;
> import org.apache.camel.util.ServiceHelper;
>
> /**
> * A processor which ensures wrapping processors is having lifecycle handled.
> - *
> - * @version
> */
> -public class WrapProcessor extends DelegateAsyncProcessor {
> +public class WrapProcessor extends DelegateAsyncProcessor implements
> Traceable {
> +
> private final Processor wrapped;
>
> public WrapProcessor(Processor processor, Processor wrapped) {
> @@ -38,6 +38,10 @@ public class WrapProcessor extends Deleg
> public String toString() {
> return "Wrap[" + wrapped + "] -> " + processor;
> }
> +
> + public String getTraceLabel() {
> + return "wrap[" + wrapped + "]";
> + }
>
> @Override
> public List next() {
>
Re: svn commit: r1420455 - /camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
Hi
Yeah not all processors should be traced. Such as Wrap, as its not
intended for tracing, but for internal purposes only.
So I am -1 on this commit also.
On Wed, Dec 12, 2012 at 5:38 AM, Willem jiang wrote:
> Hi Christian，
>
> This change breaks some unit tests of camel-core, can you have a look at them
> ?
>
> BTW,
> wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@301a69c]
> is really a good trace lab for us to use.
>
> Failed tests:
> testOk(org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest):
> expected:<[ref:myProcessor]> but
> was:<[wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@301a69c]]>
> testWithError(org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest):
> expected:<[ref:myProcessor]> but
> was:<[wrap[org.apache.camel.processor.DefaultErrorHandlerOnExceptionTraceTest$MyProcessor@10042865]]>
> testSynchronizeComplete(org.apache.camel.processor.OnCompletionGlobalTraceTest):
> expected:<[ref:myProcessor]> but
> was:<[wrap[org.apache.camel.processor.OnCompletionGlobalTraceTest$MyProcessor@4f4c55e7]]>
> testSynchronizeFailure(org.apache.camel.processor.OnCompletionGlobalTraceTest):
> expected:<[ref:myProcessor]> but
> was:<[wrap[org.apache.camel.processor.OnCompletionGlobalTraceTest$MyProcessor@256949fd]]>
>
>
>
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | 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: 姜宁willem
>
>
>
>
>
> On Wednesday, December 12, 2012 at 6:06 AM, cmuel...@apache.org
> (mailto:cmuel...@apache.org) wrote:
>
>> Author: cmueller
>> Date: Tue Dec 11 22:06:32 2012
>> New Revision: 1420455
>>
>> URL: http://svn.apache.org/viewvc?rev=1420455&view=rev
>> Log:
>> CAMEL-5844: Camel Tracer not showing some EIP names
>>
>> Modified:
>> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
>>
>> Modified:
>> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
>> URL:
>> http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java?rev=1420455&r1=1420454&r2=1420455&view=diff
>> ==
>> ---
>> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
>> (original)
>> +++
>> camel/trunk/camel-core/src/main/java/org/apache/camel/processor/WrapProcessor.java
>> Tue Dec 11 22:06:32 2012
>> @@ -19,14 +19,14 @@ package org.apache.camel.processor;
>> import java.util.List;
>>
>> import org.apache.camel.Processor;
>> +import org.apache.camel.Traceable;
>> import org.apache.camel.util.ServiceHelper;
>>
>> /**
>> * A processor which ensures wrapping processors is having lifecycle handled.
>> - *
>> - * @version
>> */
>> -public class WrapProcessor extends DelegateAsyncProcessor {
>> +public class WrapProcessor extends DelegateAsyncProcessor implements
>> Traceable {
>> +
>> private final Processor wrapped;
>>
>> public WrapProcessor(Processor processor, Processor wrapped) {
>> @@ -38,6 +38,10 @@ public class WrapProcessor extends Deleg
>> public String toString() {
>> return "Wrap[" + wrapped + "] -> " + processor;
>> }
>> +
>> + public String getTraceLabel() {
>> + return "wrap[" + wrapped + "]";
>> + }
>>
>> @Override
>> public List next() {
>>
>
>
>
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
