[jira] Resolved: (CAMEL-1529) PackageHelper.isValidVersion NPE in osgi

[ https://issues.apache.org/activemq/browse/CAMEL-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-1529. - Resolution: Fixed Fix Version/s: 1.6.1 trunk http://svn.apache.org/viewvc?rev=767824&

Re: Camel 1.6/2.0 MINA UDP issue

Hi Claus : I am working with Orton and have a UDP Mutlicast question that is also a general Camel Question. We have a multihomed computer and would like to listen on a multicast group. Is there a way to specify the localhost nic (eth1 or eth0) in the Camel From() to ensure we are listening on

Re: Camel 1.6/2.0 MINA UDP issue

Hi On Thu, Apr 23, 2009 at 10:41 PM, albiii wrote: > > > Hi Claus : > >  I am working with Orton and have a UDP Mutlicast question that is also a > general Camel Question. > We have a multihomed computer and would like to listen on a multicast group. > Is there a way to specify the localhost ni

[jira] Created: (CAMEL-1562) Introduce Channel between each EIP in the route path

Introduce Channel between each EIP in the route path Key: CAMEL-1562 URL: https://issues.apache.org/activemq/browse/CAMEL-1562 Project: Apache Camel Issue Type: New Feature Compo

[DISCUSS - Camel 2.0 - Internal API reworkings] - Channel and AsyncProcessor

Hi Camel riders As you know we are working on Camel 2.0 and we decided to do a 2nd milestone release. This gives us more time to start on some of the ideas and internal refactorings I wanted to do for Camel 2.1. After having dived really deed in the camel core codebase for the last 6+ months or l

[jira] Created: (CAMEL-1563) Message - getOut, getFault should not create empty message if none exists

Message - getOut, getFault should not create empty message if none exists - Key: CAMEL-1563 URL: https://issues.apache.org/activemq/browse/CAMEL-1563 Project: Apache Camel

[jira] Commented: (CAMEL-1562) Introduce Channel between each EIP in the route path

[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51369#action_51369 ] Claus Ibsen commented on CAMEL-1562: First cut: 768186 > Introduce Channel between each

[jira] Resolved: (CAMEL-1555) JMX Instrumentation - rework code to avoid changing the route model, so the model is the same when JMX is disabled

[ https://issues.apache.org/activemq/browse/CAMEL-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1555. Resolution: Fixed trunk: 768186 > JMX Instrumentation - rework code to avoid changing the rout

[jira] Work started: (CAMEL-1562) Introduce Channel between each EIP in the route path

[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-1562 started by Claus Ibsen. > Introduce Channel between each EIP in the route path > > >

[jira] Commented: (CAMEL-1562) Introduce Channel between each EIP in the route path

[ https://issues.apache.org/activemq/browse/CAMEL-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51370#action_51370 ] Claus Ibsen commented on CAMEL-1562: Discussion http://www.nabble.com/-DISCUSS---Camel-2.

Re: [DISCUSS - Camel 2.0 - Internal API reworkings] - Channel and AsyncProcessor

Hi Just a quick info The Channel ticket is here: https://issues.apache.org/activemq/browse/CAMEL-1562 And first initial cut committed to trunk rev: 768186