Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1694073669.1251791122173.JavaMail.jira@brutus>
Date: Tue, 1 Sep 2009 00:45:22 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-862) allow messages to be sent to an
 Endpoint over JMX
In-Reply-To: <1006492349.1219853632573.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-862.
-------------------------------

    Resolution: Won't Fix
      Assignee: Claus Ibsen  (was: Hadrian Zbarcea)

Not needed

> allow messages to be sent to an Endpoint over JMX
> -------------------------------------------------
>
>                 Key: CAMEL-862
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-862
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: jmx
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>
> to support JMX and remote JMX we'll have to be careful.
> Maybe we write a simple MXBean that lets us send a simple, concrete, String based payload?
> e.g. something kinda like this...
> {code}
> public class ExchangeMXBean {
>   private MessageMXBean in;  
>  private MessageMXBean out;
> ...
> }
> public class MessageMXBean {
>   String body;
>   String actualBodyType;
>   Map<String,String> headers;
> }
> {code}
> i.e. so over JMX (and remote JMX) we'd be able to send/receive Camel messages

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.