[jira] Created: (CAMEL-1700) Support to get the Verb and URI from the message header from the cxfrs consumer

Support to get the Verb and URI from the message header from the cxfrs consumer --- Key: CAMEL-1700 URL: https://issues.apache.org/activemq/browse/CAMEL-1700 Project: Apache C

[jira] Commented: (CAMEL-1697) Java DSL for multicast, split, aggregate does not use block explicit

[ https://issues.apache.org/activemq/browse/CAMEL-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=5#action_5 ] Claus Ibsen commented on CAMEL-1697: I have decided to keep the old behavior. It does wor

[jira] Issue Comment Edited: (CAMEL-1697) Java DSL for multicast, split, aggregate does not use block explicit

[ https://issues.apache.org/activemq/browse/CAMEL-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=5#action_5 ] Claus Ibsen edited comment on CAMEL-1697 at 6/12/09 1:23 AM: - I h

[jira] Resolved: (CAMEL-1697) Java DSL for multicast, split, aggregate does not use block explicit

[ https://issues.apache.org/activemq/browse/CAMEL-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1697. Resolution: Fixed trunk: 784038. > Java DSL for multicast, split, aggregate does not use block

Re: in.body.bean - camel simple language

Is the OGNL language fully supported in Camel or do we have restrictions ? http://www.opensymphony.com/ognl/html/LanguageGuide/index.html Regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer * blog : http://cmoulliard.blogspot.com On Thu, J

Re: in.body.bean - camel simple language

On Fri, Jun 12, 2009 at 12:18 PM, Charles Moulliard wrote: > Is the OGNL language fully supported in Camel or do we have restrictions ? > > http://www.opensymphony.com/ognl/html/LanguageGuide/index.html > I am not aware of any restrictions. So assume fully supported. But no guarantees. > Regards

[jira] Created: (CAMEL-1701) Let camel spring auto detect any InterceptStrategy spring beans and auto use them on startup

Let camel spring auto detect any InterceptStrategy spring beans and auto use them on startup Key: CAMEL-1701 URL: https://issues.apache.org/activemq/browse/CAMEL-1701

How to propagate headers received in a camel bean ?

Hi, I' m a little bit confused about how to propagate headers received in a camel bean ? Here is my example. Is it correct what I do or not public Request createRequest( @Header(value = "messageType") String messageType, --> header received @Header(value = "CamelFileN

Re: How to propagate headers received in a camel bean ?

On Fri, Jun 12, 2009 at 1:23 PM, Charles Moulliard wrote: > Hi, > > I' m a little bit confused about how to propagate headers received in a > camel bean ? > > Here is my example. Is it correct what I do or not > >    public Request createRequest( >           �...@header(value = "messageType") Strin

[jira] Created: (CAMEL-1702) Mirgrate Camel EIP decorated headers to properties

Mirgrate Camel EIP decorated headers to properties -- Key: CAMEL-1702 URL: https://issues.apache.org/activemq/browse/CAMEL-1702 Project: Apache Camel Issue Type: Improvement Component

[VOTE] Release Apache Camel 2.0-M2

A long awaited apache-camel-2.0-M2 is finally out with 220 new features, improvements and bug fixes. Please find the staging repo here: https://repository.apache.org/content/groups/public/org/apache/camel/ The tarballs are here https://repository.apache.org/content/groups/public/org/apache/cam

[jira] Resolved: (CAMEL-1701) Let camel spring auto detect any InterceptStrategy spring beans and auto use them on startup

[ https://issues.apache.org/activemq/browse/CAMEL-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1701. Resolution: Fixed trunk: 784101. And started a wiki page about it http://cwiki.apache.org/conf

Re: [VOTE] Release Apache Camel 2.0-M2

+1 On Fri, Jun 12, 2009 at 2:46 PM, Hadrian Zbarcea wrote: > A long awaited apache-camel-2.0-M2 is finally out with 220 new features, > improvements and bug fixes. > > Please find the staging repo here: > https://repository.apache.org/content/groups/public/org/apache/camel/ > > The tarballs are he

[jira] Commented: (CAMEL-1675) Created a new camel printer component that supports document/image printing with copies, stationary and sides choices.

[ https://issues.apache.org/activemq/browse/CAMEL-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52229#action_52229 ] Ashwin Karpe commented on CAMEL-1675: - Hi Hadrian, Claus, Does everything look ok? Do yo

[jira] Commented: (CAMEL-1675) Created a new camel printer component that supports document/image printing with copies, stationary and sides choices.

[ https://issues.apache.org/activemq/browse/CAMEL-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52231#action_52231 ] Claus Ibsen commented on CAMEL-1675: Hi I personally do not have time to look into a new

Re: [VOTE] Release Apache Camel 2.0-M2

On Fri, Jun 12, 2009 at 6:46 AM, Hadrian Zbarcea wrote: > A long awaited apache-camel-2.0-M2 is finally out with 220 new features, > improvements and bug fixes. > > Please find the staging repo here: > https://repository.apache.org/content/groups/public/org/apache/camel/ > > The tarballs are here >

[jira] Assigned: (CAMEL-1692) Use handled by default on dead letter channel

[ https://issues.apache.org/activemq/browse/CAMEL-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-1692: -- Assignee: Claus Ibsen > Use handled by default on dead letter channel > ---

Re: [VOTE] Release Apache Camel 2.0-M2

The javadocs jars do not contain the required LICENSE / NOTICE files. At least, the one I've just checked https://repository.apache.org/content/groups/public/org/apache/camel/camel-core/2.0-M2/camel-core-2.0-M2-javadoc.jar On Fri, Jun 12, 2009 at 14:46, Hadrian Zbarcea wrote: > A long awaited apac

Re: [VOTE] Release Apache Camel 2.0-M2

Please be aware, that although the vote has not been finalized, the 2.0-M2 is in the nexus public repo, not the staging repo as it should be. This is due to my mistake this morning, I did not only a close on the staged release, but also a promote, which is only done after the vote passes.