Re: Problem with DefaultCamelContext EndpointRegistry

2013-07-02 Thread Chris Wolf
Claus, Thanks, but the fact that attempting to add another instance of the same Endpoint type results in the name getting and instance number appended means that some consideration must have been given to accommodating multiple instances of the same Endpoint in the registry, right? In any case, I

Re: Problem with DefaultCamelContext EndpointRegistry

2013-06-14 Thread Claus Ibsen
Only singleton endpoints should be in the registry. Non singleton is prototype based and therefore a new instance is created when you call getEndpoint. On Wed, Jun 12, 2013 at 7:41 PM, Chris Wolf wrote: > Ok, have a partial answer - since my Endpoint is not a singleton, I see that > DefaultCam

Re: Problem with DefaultCamelContext EndpointRegistry

2013-06-12 Thread Chris Wolf
Ok, have a partial answer - since my Endpoint is not a singleton, I see that DefaultCamelContext.getEndpointKey(String uri, Endpoint endpoint) appends that "%3A2" - i.e. ":2" - which appears to be an instance qualifier. The trouble is, DefaultEndpoint.getEndpointUri() will always return the URI *w

Problem with DefaultCamelContext EndpointRegistry

2013-06-12 Thread Chris Wolf
I am trying to develop a new component, but it needs to be able to have it's endpoint be registered in the CamelContext endpoint registry. Whenever the runtime tries to call DefaultCamelContext.getEndpoint(String uri) it returns null, even though, in the debugger, I can expand DefaultCamelContext