Ok I attached the patch to the Jira issue.
smullins7 wrote:
>
> Nevermind, just read in the docs that I should attach my fix to the jira
> and fire off an email to the forum group :)
>
> smullins7 wrote:
>>
>> I created CAMEL-1450; I can't actually assign this
Nevermind, just read in the docs that I should attach my fix to the jira and
fire off an email to the forum group :)
smullins7 wrote:
>
> I created CAMEL-1450; I can't actually assign this to anyone but mind if I
> take a stab at it? Should I comment on the jira or this thread
I created CAMEL-1450; I can't actually assign this to anyone but mind if I
take a stab at it? Should I comment on the jira or this thread when I have
something ready for review?
James.Strachan wrote:
>
> 2009/3/11 smullins7 :
>>
>> Yep that sounds fine to me. Should I
Yep that sounds fine to me. Should I create a jira for this? I haven't read
any information for developers on this project yet (will do that right now).
Claus Ibsen-2 wrote:
>
> On Wed, Mar 11, 2009 at 4:35 PM, smullins7 wrote:
>>
>> No spring is not creating my endpo
r the
ManagedEndpoint with the mbeanserver. Maybe there's a way to check if the
endpoint is a MangedResource; if it is then register the endpoint, if its
not then wrap it in a MangedEndpoint?
James.Strachan wrote:
>
> 2009/3/10 smullins7 :
>>
>> Hey thanks for the quick re
ried using the
in my camelContext to specify my mbean server domain but that had
no affect.
My endpoint should not be spring wired, my custom component will create the
endpoint so only my component is spring wired.
Claus Ibsen-2 wrote:
>
> On Mon, Mar 9, 2009 at 10:16 PM, smullins7 wrote
Hello, I have custom endpoints developed that I would like to expose as
mbeans through JMX. Currently, only the attributes of ManagedEndpoint show
up. What is the easiest way to get a custom endpoint exposed in jmx while
piggy-backing off the existing mbean server/naming strategy/etc supplied by
