toString in camel-mail MailConverters

The toString method in org.apache.camel.component.mail.MailConverters is overloaded to handle both javax.mail.Message and javax.mail.Multipart. The implementation fo the Message version checks for a MimeMultipart instance and if so uses the first body part. The implementation of the Multipart versi

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036619#comment-13036619 ] Mark Ford commented on CAMEL-3476: -- I think the addition of the consumer to the

[jira] [Commented] (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036617#comment-13036617 ] Mark Ford commented on CAMEL-3325: -- I updated both. Can you review and let me kno

[jira] [Commented] (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036427#comment-13036427 ] Mark Ford commented on CAMEL-3325: -- I have time and karma. I'll look at upd

[jira] [Commented] (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029323#comment-13029323 ] Mark Ford commented on CAMEL-3325: -- Is this issue waiting for anything further fro

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011303#comment-13011303 ] Mark Ford commented on CAMEL-3476: -- I don't think you need two sets of cr

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010460#comment-13010460 ] Mark Ford commented on CAMEL-3476: -- I think we've made a good deal of progress.

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010309#comment-13010309 ] Mark Ford commented on CAMEL-3476: -- I don't understand why the producer would c

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010088#comment-13010088 ] Mark Ford commented on CAMEL-3476: -- I was not disappointed in your decision but onl

[jira] [Commented] (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009923#comment-13009923 ] Mark Ford commented on CAMEL-3476: -- Christian, I don't share your opinions an

Re: Advice for CAMEL-3476

What do you mean by implementing it as a connector? On Wed, Mar 16, 2011 at 2:46 AM, Willem Jiang wrote: > Hi Christian, > > It looks like the subscription can be implemented as a connector. > In this way user could configure the connector as they want and your SNS > component could be free to th

Re: Advice for CAMEL-3476

I thought this was settled in the issue comments already. You haven't raised any new points except the percentage of code devoted to the consumer which I think is irrelevant. That code is only exercised when the user provides the appropriate switches and it also may shrink when Tracy refactors the

[jira] Commented: (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001417#comment-13001417 ] Mark Ford commented on CAMEL-3476: -- Doesn't the SNS code cache the AWS key in

[jira] Commented: (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001205#comment-13001205 ] Mark Ford commented on CAMEL-3476: -- I think there's value in having a way to s

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

I would like to see a branch of camel 2.6.x that was kept up to date with major bug fixes since I have some projects that are stuck on 1.5. As for JUnit, I don't see what needs to be done since it's backwards compatible, right? The annotations are much cleaner but I don't see a pressing need to mi

[jira] Updated: (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

[ https://issues.apache.org/jira/browse/CAMEL-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3476: - Attachment: camel-aws-3476.txt Attached is my camel-sns contribution that has been repackaged by Tracy

karma for wiki

Hi, I've recently completed the ICLA and see my name in the list of CLA recipients. I'd like to get karma to make edits to the camel-jmx documentation. I'd like to incorporate the documentation from CAMEL-3325 (https://issues.apache.org/jira/browse/CAMEL-3325) once the patch is reviewed and commit

[jira] Created: (CAMEL-3476) Contribute camel-sns component to the new camel-aws component.

Affects Versions: 2.6.0 Reporter: Mark Ford Priority: Minor CAMEL-3468 contributes a new component for interacting with the Amazon SQS service. The camel-sns component allows users to publish/subscribe to topics on Amazon's Simple Notification Service. This co

[jira] Commented: (CAMEL-3468) New camel-aws component

[ https://issues.apache.org/jira/browse/CAMEL-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976256#action_12976256 ] Mark Ford commented on CAMEL-3468: -- @Christian - I'll create the issue to add

[jira] Updated: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3325: - Attachment: (was: camel-3325-patch.txt) > camel-jmx: Auto creation of a monitor bean via endpo

[jira] Updated: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3325: - Attachment: camel-3325-patch-sans-lang.txt Good suggestion by Richard to remove the commons-lang

patch for camel-3325

I finally got around to finishing up the code for the previously proposed enhancements to the camel-jmx component. I think this completes the work I had originally envisioned for this component. I'd be interested in hearing if there are any other suggestions for new functionality. I haven't had a c

[jira] Updated: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/jira/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3325: - Attachment: camel-3325-patch.txt The patch provides for all of the functionality described in the issue

[jira] Commented: (CAMEL-3468) New camel-aws component

[ https://issues.apache.org/jira/browse/CAMEL-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975600#action_12975600 ] Mark Ford commented on CAMEL-3468: -- You're welcome to take as much or as litt

[jira] Commented: (CAMEL-3468) New camel-aws component

[ https://issues.apache.org/jira/browse/CAMEL-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975561#action_12975561 ] Mark Ford commented on CAMEL-3468: -- I created one for the SNS back in May 2010. It&

[jira] Commented: (CAMEL-3331) xslt component - Support URI inline strings as resources

[ https://issues.apache.org/activemq/browse/CAMEL-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63319#action_63319 ] Mark Ford commented on CAMEL-3331: -- I can't imagine anyone configuring the xslt

[jira] Updated: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

[ https://issues.apache.org/activemq/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3325: - Component/s: camel-jmx Affects Version/s: 2.6.0 > camel-jmx: Auto creation of a moni

Re: [jira] Created: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

t 11:47 AM, Mark Ford (JIRA) wrote: > camel-jmx: Auto creation of a monitor bean via endpoint properties > -- > >                 Key: CAMEL-3325 >                 URL: https://issues.apache.org/activemq/browse/CAMEL-3

[jira] Created: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

: New Feature Reporter: Mark Ford Priority: Minor The current version of the camel-jmx component allows for the forwarding of JMX notifications from an mbean into the route. In addition to receiving notifications, a user may want to monitor an mbean. The consumer

[jira] Updated: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3236: - Attachment: camel-jmx-tstamp-attempt3.txt Wow, three attempts to fix a timestamp issue. This is

[jira] Updated: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3236: - Attachment: camel-jmx-tstamp-jdk15.txt I fixed the timestamp by using XSLT to strip the timestamp

[jira] Commented: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63129#action_63129 ] Mark Ford commented on CAMEL-3236: -- I have other tests where I'm stripping the

[jira] Commented: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63121#action_63121 ] Mark Ford commented on CAMEL-3236: -- It would be easier if you'd just move to my

[jira] Commented: (CAMEL-3172) Create forthcoming Camel-JMX component documentation page

[ https://issues.apache.org/activemq/browse/CAMEL-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63109#action_63109 ] Mark Ford commented on CAMEL-3172: -- Claus, Are you looking for some samples for the

[jira] Updated: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3236: - Attachment: camel-jmx-timestamp.txt The timestamp error is likely due to the difference in our

[jira] Commented: (CAMEL-2737) xslt component - Add option for templateCache to control if template is cached or loaded on each invocation

[ https://issues.apache.org/activemq/browse/CAMEL-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62930#action_62930 ] Mark Ford commented on CAMEL-2737: -- Reloading on every exchange is good for develop

[jira] Commented: (CAMEL-2405) JMX notification listener to route JMX events to camel

[ https://issues.apache.org/activemq/browse/CAMEL-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62795#action_62795 ] Mark Ford commented on CAMEL-2405: -- This should be resolved with CAMEL-3236 &

[jira] Commented: (CAMEL-3255) Add property to DefaultCamelContext to allow for lazy loading of the DefaultTypeConverter

[ https://issues.apache.org/activemq/browse/CAMEL-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62726#action_62726 ] Mark Ford commented on CAMEL-3255: -- Claus, I respectively disagree that having a

[jira] Commented: (CAMEL-3255) Add property to DefaultCamelContext to allow for lazy loading of the DefaultTypeConverter

[ https://issues.apache.org/activemq/browse/CAMEL-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62693#action_62693 ] Mark Ford commented on CAMEL-3255: -- Thanks for implementing this and adding the xml sup

[jira] Updated: (CAMEL-3255) Add property to DefaultCamelContext to allow for lazy loading of the DefaultTypeConverter

[ https://issues.apache.org/activemq/browse/CAMEL-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3255: - Attachment: patch.txt Patch adds the property to the context and encapsulates the loading of the

[jira] Created: (CAMEL-3255) Add property to DefaultCamelContext to allow for lazy loading of the DefaultTypeConverter

Project: Apache Camel Issue Type: New Feature Components: camel-core Affects Versions: 2.4.0, 2.3.0, 2.2.0 Reporter: Mark Ford Priority: Minor The loading of type converters was changed from a lazy loading to an up front loading in a Camel 2.2

Re: [VOTE] Release Apache Camel 2.5.0

It looks like this behavior changed in Camel 2.2. I noticed it when switching my camel-jmx component from 2.1 to 2.5-SNAPSHOT. Suddenly my suite of unit tests went from 1 second to 6 seconds. I can recreate this behavior with versions 2.2, 2.3, and 2.5-SNAPSHOT. I didn't try with 2.4. The initial

[jira] Updated: (CAMEL-3236) Camel JMX Component

[ https://issues.apache.org/activemq/browse/CAMEL-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford updated CAMEL-3236: - Attachment: camel-jmx-patch.txt I have repackaged the code from my google code project so it matches

[jira] Commented: (CAMEL-2405) JMX notification listener to route JMX events to camel

[ https://issues.apache.org/activemq/browse/CAMEL-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62470#action_62470 ] Mark Ford commented on CAMEL-2405: -- I am currently preparing to contribute

[jira] Commented: (CAMEL-2922) XMPPConsumer does not remove the message which causes OOME with XMPP

[ https://issues.apache.org/activemq/browse/CAMEL-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60643#action_60643 ] Mark Ford commented on CAMEL-2922: -- I haven't had a chance to look at integratin

[jira] Commented: (CAMEL-1467) OutOfMemory Exception in XMPP Component

[ https://issues.apache.org/activemq/browse/CAMEL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60453#action_60453 ] Mark Ford commented on CAMEL-1467: -- Here's a relevant defect from the smack libra

[jira] Reopened: (CAMEL-1467) OutOfMemory Exception in XMPP Component

[ https://issues.apache.org/activemq/browse/CAMEL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Ford reopened CAMEL-1467: -- The patch for this bug was removed in revision 779121. The result is that the XMPPConsumer does not