On Tue, Jul 7, 2009 at 4:53 PM, Claus Ibsen<[email protected]> wrote:
> On Tue, Jul 7, 2009 at 4:47 PM, siva naresh<[email protected]> wrote:
>>
>> someNode.getId() is called during debug interceptor call and it should be
>> returning whatever was set for that node during initialization of
>> camelcontext.
>>
> Hi
>
> Let me add an unit test in the Java DSL that sets some custom ids.
> And see if I can get them later.
from("direct:start").id("A")
.to("log:foo").id("B")
.to("mock:result").id("C");
Yeah it looks like the A is set on the route instead of the
"direct:start" endpoint
But you can get there as it would just be a RouteDefintion and you can
get the input by getInputs().get(0).
B and C looks fine to me.
>
>
>> ----
>> Siva Naresh.
>>
>>
>>
>> James.Strachan wrote:
>>>
>>> 2009/7/7 siva naresh <[email protected]>:
>>>>
>>>> The ids are important to identify the endpoint to a front end tooling
>>>> system.
>>>>
>>>> Using the camel naming system. we get null ids for all the endpoints in
>>>> the
>>>> multicast case for example.
>>>
>>> An even easier fix then, replace the code which does
>>>
>>> someNode.getId()
>>>
>>> with
>>>
>>> someNode.idOrCreate()
>>>
>>> :)
>>>
>>> --
>>> James
>>> -------
>>> http://macstrac.blogspot.com/
>>>
>>> Open Source Integration
>>> http://fusesource.com/
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/id%28%29-in-Java-dsl-tp24371134p24374391.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
