Re: MBean Runtime Exception in getRoutePolicyList

Also, does anybody know what the actual issue was and if there are any implications to it, if we do not upgrade to the latest version? We haven't seen any message failures due to this issue though. Thanks. ----- - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/

Re: MBean Runtime Exception in getRoutePolicyList

We are using v2.7.1. Do you remember in which version this was fixed? Thanks. - - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/MBean-Runtime-Exception-in-getRoutePolicyList-tp4717413p4724530.html Sent from the Camel - Users mailing list archive at Nabble.com.

MBean Runtime Exception in getRoutePolicyList

8) at java.lang.StringBuilder.delete(StringBuilder.java:255) at org.apache.camel.management.mbean.ManagedRoute.getRoutePolicyList(ManagedRoute.java:121) at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source) ----- - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/

Attachment Names not Encoded Correctly

If attachment file names contain unicode characters, they do not appear correctly encoded in the message. I have created a JIRA ticket here: https://issues.apache.org/jira/browse/CAMEL-4007 - - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/Attachment-Names-not

Re: Encoding the Sender & the Recipient Email Addresses

Thanks, Claus. I have created a JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-3985 I also have a patch for this issue, and will submit it as soon as possible. Thanks. - - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/Encoding-the-Sender-the-Recipient

Encoding the Sender & the Recipient Email Addresses

doesn't seem to be implemented. However, encoding the string and then setting them as header values works just fine. Is there any way to do this, other than encoding the header values & then setting them? Thanks. - - Karthz -- View this message in context: http://camel.465427.n5.n

Re: InterceptSendToEndpoint - Http Component

Great, thank you. Just curious - in which class is this fix needed? - - Karthz -- View this message in context: http://camel.465427.n5.nabble.com/InterceptSendToEndpoint-Http-Component-tp3296620p3297052.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: InterceptSendToEndpoint - Http Component

Thanks, Claus. But, I want the original route skipped only when there's an exception. Otherwise, it should send the message as normal. Should I still set skipSendToOriginalEndpoint? Thanks. ----- - Karthz -- View this message in context: http://camel.465427.n5.nabbl

InterceptSendToEndpoint - Http Component

, and not the http component, then it works fine. In the above route, this change does exactly what I want it to do. It intercepts before the method, and the method never gets executed in case of an exception. So, what's the correct way to intercept something that's

Http POST

would the message body be, in the request I receive? I thought the message body would be in the HttpServletRequest object as attributes, or params, but none of them have what I am looking for. Any ideas? Thanks. - - Karthz -- View this message in context: http://camel.465427.n5.nabble.com

Exchange Timeouts

How do I configure (total) timeouts for exchanges? I have different components in the routes, and I do not want to configure component timeouts. What I need is, to configure a total timeout so that any exchange would stop/exit the route if it times out. Thanks. - - Karthz -- View this

Re: Comma in email names

JIRA Ticket for this bug: https://issues.apache.org/activemq/browse/CAMEL-3199 -- View this message in context: http://camel.465427.n5.nabble.com/Comma-in-email-names-tp3198928p3199946.html Sent from the Camel - Users mailing list archive at Nabble.com.

Comma in email names

Hi, In camel-mail, if there's a comma in the "name" part of the email, like "Doe, John" in Camel MailBinding, it gets split into two separate recipients "Doe" and "John"        // we support that multi recipient can be given as a string separated by comma or semicolon         String[]