[jira] Created: (CAMEL-1447) DSL name change - tryBlock, handleBlock instead of handle, and maybe add a finallyBlock

DSL name change - tryBlock, handleBlock instead of handle, and maybe add a finallyBlock --- Key: CAMEL-1447 URL: https://issues.apache.org/activemq/browse/CAMEL-1447

[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-tabpanel&focusedCommentId=50415#action_50415 ] Claus Ibsen commented on CAMEL-1446: In fact we dont even need the @TypeConverter annotat

[jira] Updated: (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:all-tabpanel ] Claus Ibsen updated CAMEL-1446: --- Description: See this article page 4, listening 6 http://architects.dzone.com/articles/fuse-esb-4

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

Bean Binding - Add annotation @TypeConverter so end users easily can get access to the type converter - Key: CAMEL-1446 URL: https://issues.apache.org/activemq/bro

[jira] Assigned: (CAMEL-1427) java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext

[ https://issues.apache.org/activemq/browse/CAMEL-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-1427: --- Assignee: Willem Jiang > java.lang.IllegalStateException: BeanFactory not initialized or

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: Co

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 t

[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

[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-tabpanel&focusedCommentId=50399#action_50399 ] Charles Moulliard commented on CAMEL-1442: -- @All, Camel-bindy wiki documentation ha

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:45 PM, orton wrote: > > > ≥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 no

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 more?

[jira] Updated: (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:all-tabpanel ] Charles Moulliard updated CAMEL-1442: - Attachment: crlf_noModelReset.patch - Class ConvertSeparator has been renamed into Co

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:25 PM, Claus Ibsen wrote: > On Tue, Mar 10, 2009 at 2:19 PM, orton 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...

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:19 PM, orton 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 in the

[jira] Updated: (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:all-tabpanel ] Charles Moulliard updated CAMEL-1442: - Attachment: (was: crlf_noModelReset.patch) > unmarshaling of data always send the

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. > Whe

[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-tabpanel&focusedCommentId=50392#action_50392 ] Charles Moulliard commented on CAMEL-1442: -- +1 Claus, I will add new parameter in t

[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-tabpanel&focusedCommentId=50391#action_50391 ] Claus Ibsen commented on CAMEL-1442: Charles could you make the CR LF configurable. What

[jira] Updated: (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:all-tabpanel ] Charles Moulliard updated CAMEL-1442: - Attachment: crlf_noModelReset.patch > unmarshaling of data always send the last occur

[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-tabpanel&focusedCommentId=50390#action_50390 ] Charles Moulliard commented on CAMEL-1442: -- and no carriage return (CRLF) was added

[jira] Resolved: (CAMEL-1395) Refactor - All models classes xxxType renamed to xxxDefinition

[ https://issues.apache.org/activemq/browse/CAMEL-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1395. Resolution: Fixed Hadrian the build of M1 can start > Refactor - All models classes xxxType re

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 1.6

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

[ https://issues.apache.org/activemq/browse/CAMEL-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1444. Resolution: Fixed trunk: r752068 1.x: Committed revision 752070. > camel-mina - UDP protocol

[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 U

Re: Camel 1.6/2.0 MINA UDP issue

BTW I think I have seen some UDP issue with camel-mina about acquiring/releasing mina byte buffer. Damm that API is not so easy to work with - should be improved in mina 2.0 So it could relate to your issue as well On Tue, Mar 10, 2009 at 8:43 AM, Claus Ibsen wrote: > On Tue, Mar 10, 2009 at 2:3

[jira] Commented: (CAMEL-1443) Unable to resolve scripting languages in OSGi environment

[ https://issues.apache.org/activemq/browse/CAMEL-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50381#action_50381 ] Willem Jiang commented on CAMEL-1443: - Thanks for point it out. I just checked the code,

[jira] Assigned: (CAMEL-1443) Unable to resolve scripting languages in OSGi environment

[ https://issues.apache.org/activemq/browse/CAMEL-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned CAMEL-1443: --- Assignee: Willem Jiang > Unable to resolve scripting languages in OSGi environment >

Re: Camel 1.6/2.0 MINA UDP issue

On Tue, Mar 10, 2009 at 2:39 AM, orton 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 from a > si