Camel 2.0 API - Discuss - Exchange.getException() change to Exception

Hi The Exchange.getException() method is based on Throwable. I think this is wrong and we should change it to Exception. We should let the java.lang.Error left alone to the JDK itself to handle it, so end users cannot try .. catch(Throwable) and thus hide java.lang.OutOfMemoryError etc. The

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:39 AM, orton o_hu...@yahoo.com wrote: Hi, I've been trying to use the MINA component for UDP data delivery but have been having some issues and was wondering if anyone else has seen this error. I'm sending small packets (100Bytes) as fast as I can (sequentially

[jira] Created: (CAMEL-1444) camel-mina - UDP protocol could have an issue if used in same camel context as both client and server sending to localhost

camel-mina - UDP protocol could have an issue if used in same camel context as both client and server sending to localhost -- Key: CAMEL-1444

Re: Camel 1.6/2.0 MINA UDP issue

Hi I have commited a fix to UPD in camel-mina on both 1.6.1 and 2.0 https://issues.apache.org/activemq/browse/CAMEL-1444 Could you try it out on your system? 2.0-SNAPSHOT is automatic build and published at apache maven snapshot repo. http://camel.apache.org/download.html I cant remember if

[jira] Commented: (CAMEL-1442) unmarshaling of data always send the last occurence of the stream

[ https://issues.apache.org/activemq/browse/CAMEL-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50390#action_50390 ] Charles Moulliard commented on CAMEL-1442: -- and no carriage return (CRLF) was added

Re: Camel 1.6/2.0 MINA UDP issue

What version of Camel and Mina are you using? I tried it out on the Camel 1.6 bin release and I compiled the Camel 2.0 snapshot in svn and both appeared to have the same problem... mina-core for both appear to be 1.1.7 Mina is in the works of doing a Mina 2.0 that might be much better. When

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:19 PM, orton o_hu...@yahoo.com wrote: What version of Camel and Mina are you using? I tried it out on the Camel 1.6 bin release and I compiled the Camel 2.0 snapshot in svn and both appeared to have the same problem... mina-core for both appear to be 1.1.7 Mina is

Re: Camel 1.6/2.0 MINA UDP issue

≥Oh if you do NOT use the transferExchange=true option. eg if you send ≥regular payload with Camel 1.6.0. ≥But yet again would be nice if you try the comitted fix. Hi Claus, am updating my Camel 2.0 code from repository and compiling now. Can you explain the transferExchange comment some

[jira] Commented: (CAMEL-1442) unmarshaling of data always send the last occurence of the stream

[ https://issues.apache.org/activemq/browse/CAMEL-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50399#action_50399 ] Charles Moulliard commented on CAMEL-1442: -- @All, Camel-bindy wiki documentation

[jira] Created: (CAMEL-1445) Using the cached stream in the http component to avoid the OutOfMemoryError

Using the cached stream in the http component to avoid the OutOfMemoryError --- Key: CAMEL-1445 URL: https://issues.apache.org/activemq/browse/CAMEL-1445 Project: Apache Camel

Re: Camel 1.6/2.0 MINA UDP issue

It marshal the entire Exchange, eg the container object in Camel used when routing messages. Its an option to use MINA as a kind of bridge between camel instances. So you can keep headers, properties etc. when you send the Exchange using Mina. Normally you only send the payload itself, eg the

Re: Camel 1.6/2.0 MINA UDP issue

One more thing... Right now, I'm just catching all Exceptions and printing them out. When the component stops sending, usually no exceptions are thrown... Not sure if they are getting swallowed up somewhere lower. However, one time I ran it, for some reason I did get this: Exception caught:

[jira] Commented: (CAMEL-1446) Bean Binding - Add annotation @TypeConverter so end users easily can get access to the type converter

[ https://issues.apache.org/activemq/browse/CAMEL-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=50415#action_50415 ] Claus Ibsen commented on CAMEL-1446: In fact we dont even need the @TypeConverter