You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Fernando Ribeiro <we...@fernandoribeiro.eti.br> on 2011/01/04 17:53:56 UTC
"Failed to resolve endpoint" on ServiceMix 4.2
Hello,
I've found an interesting issue when deploying a route in ServiceMix 4.2,
which I discussed at http://fusesource.com/forums/thread.jspa?threadID=2493.
The fix was adding an OSGi reference manually to the beans.xml file, which
was awkward because I expected all components, for example, to be loaded
before any routes that use them to be started.
If you prefer me to take this discussion to the ServiceMix mailing lists
instead, please advise.
Thanks,
Fernando
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
I've created an issue at https://issues.apache.org/jira/browse/CAMEL-3517 for
this matter. Thanks.
On Wed, Jan 5, 2011 at 9:13 AM, Fernando Ribeiro <
webmaster@fernandoribeiro.eti.br> wrote:
> JB,
>
> No problems, will actually blog about it next, just wanted to know if
> anyone here can help me with the following questions about the issue from
> the original discussion:
>
> 1. Is this the expected behavior, or should all components actually be
> [made] available before any routes are built? Should it be reported as a bug
> and/or an improvement?
>
> 2. I had worked around the issue by accessing the endpoint in Java code
> (getEndpoint("restlet")), how does it work there?
>
> 3. How exactly does the import in question fix the issue? [it worries me
> not to know if it ensures the component will be loaded before the route is
> started or just launches before it].
>
> Thanks,
>
> Fernando
>
> On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi Fernando,
>>
>> thanks for spotting that, it can help Camel/ServiceMix users :)
>>
>> Regards
>> JB
>>
>>
>> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>>
>>> Hello,
>>>
>>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>>> which I discussed at
>>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>>
>>> The fix was adding an OSGi reference manually to the beans.xml file,
>>> which
>>> was awkward because I expected all components, for example, to be loaded
>>> before any routes that use them to be started.
>>>
>>> If you prefer me to take this discussion to the ServiceMix mailing lists
>>> instead, please advise.
>>>
>>> Thanks,
>>>
>>> Fernando
>>>
>>>
>
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
Agreed, thanks!
On Sun, Jan 9, 2011 at 11:22 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Moved to SMX jira tracker as its an issue related to its host
> container (OSGi) and how it startup bundles.
>
>
> On Sun, Jan 9, 2011 at 12:54 PM, Fernando Ribeiro
> <we...@fernandoribeiro.eti.br> wrote:
> > I've created an issue at
> https://issues.apache.org/jira/browse/CAMEL-3517 for
> > this matter. Thanks.
> >
> > On Thu, Jan 6, 2011 at 1:28 AM, Fernando Ribeiro <
> > webmaster@fernandoribeiro.eti.br> wrote:
> >
> >> Can you please help with questions 1 and 3? Thanks.
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
> >> Date: Wed, Jan 5, 2011 at 9:13 AM
> >> Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
> >> To: users@camel.apache.org
> >>
> >>
> >> JB,
> >>
> >> No problems, will actually blog about it next, just wanted to know if
> >> anyone here can help me with the following questions about the issue
> from
> >> the original discussion:
> >>
> >> 1. Is this the expected behavior, or should all components actually be
> >> [made] available before any routes are built? Should it be reported as a
> bug
> >> and/or an improvement?
> >>
> >> 2. I had worked around the issue by accessing the endpoint in Java code
> >> (getEndpoint("restlet")), how does it work there?
> >>
> >> 3. How exactly does the import in question fix the issue? [it worries me
> >> not to know if it ensures the component will be loaded before the route
> is
> >> started or just launches before it].
> >>
> >> Thanks,
> >>
> >> Fernando
> >>
> >> On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb@nanthrax.net
> >wrote:
> >>
> >>> Hi Fernando,
> >>>
> >>> thanks for spotting that, it can help Camel/ServiceMix users :)
> >>>
> >>> Regards
> >>> JB
> >>>
> >>>
> >>> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
> >>>
> >>>> Hello,
> >>>>
> >>>> I've found an interesting issue when deploying a route in ServiceMix
> 4.2,
> >>>> which I discussed at
> >>>> http://fusesource.com/forums/thread.jspa?threadID=2493.
> >>>>
> >>>> The fix was adding an OSGi reference manually to the beans.xml file,
> >>>> which
> >>>> was awkward because I expected all components, for example, to be
> loaded
> >>>> before any routes that use them to be started.
> >>>>
> >>>> If you prefer me to take this discussion to the ServiceMix mailing
> lists
> >>>> instead, please advise.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Fernando
> >>>>
> >>>>
> >>
> >>
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Claus Ibsen <cl...@gmail.com>.
Moved to SMX jira tracker as its an issue related to its host
container (OSGi) and how it startup bundles.
On Sun, Jan 9, 2011 at 12:54 PM, Fernando Ribeiro
<we...@fernandoribeiro.eti.br> wrote:
> I've created an issue at https://issues.apache.org/jira/browse/CAMEL-3517 for
> this matter. Thanks.
>
> On Thu, Jan 6, 2011 at 1:28 AM, Fernando Ribeiro <
> webmaster@fernandoribeiro.eti.br> wrote:
>
>> Can you please help with questions 1 and 3? Thanks.
>>
>>
>> ---------- Forwarded message ----------
>> From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
>> Date: Wed, Jan 5, 2011 at 9:13 AM
>> Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
>> To: users@camel.apache.org
>>
>>
>> JB,
>>
>> No problems, will actually blog about it next, just wanted to know if
>> anyone here can help me with the following questions about the issue from
>> the original discussion:
>>
>> 1. Is this the expected behavior, or should all components actually be
>> [made] available before any routes are built? Should it be reported as a bug
>> and/or an improvement?
>>
>> 2. I had worked around the issue by accessing the endpoint in Java code
>> (getEndpoint("restlet")), how does it work there?
>>
>> 3. How exactly does the import in question fix the issue? [it worries me
>> not to know if it ensures the component will be loaded before the route is
>> started or just launches before it].
>>
>> Thanks,
>>
>> Fernando
>>
>> On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>>
>>> Hi Fernando,
>>>
>>> thanks for spotting that, it can help Camel/ServiceMix users :)
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>>>
>>>> Hello,
>>>>
>>>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>>>> which I discussed at
>>>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>>>
>>>> The fix was adding an OSGi reference manually to the beans.xml file,
>>>> which
>>>> was awkward because I expected all components, for example, to be loaded
>>>> before any routes that use them to be started.
>>>>
>>>> If you prefer me to take this discussion to the ServiceMix mailing lists
>>>> instead, please advise.
>>>>
>>>> Thanks,
>>>>
>>>> Fernando
>>>>
>>>>
>>
>>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for that Fernando.
I will try to take a look next week.
Regards
JB
-----Original Message-----
From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
Date: Sun, 9 Jan 2011 09:54:59
To: <us...@servicemix.apache.org>
Reply-To: users@servicemix.apache.org
Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
I've created an issue at https://issues.apache.org/jira/browse/CAMEL-3517 for
this matter. Thanks.
On Thu, Jan 6, 2011 at 1:28 AM, Fernando Ribeiro <
webmaster@fernandoribeiro.eti.br> wrote:
> Can you please help with questions 1 and 3? Thanks.
>
>
> ---------- Forwarded message ----------
> From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
> Date: Wed, Jan 5, 2011 at 9:13 AM
> Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
> To: users@camel.apache.org
>
>
> JB,
>
> No problems, will actually blog about it next, just wanted to know if
> anyone here can help me with the following questions about the issue from
> the original discussion:
>
> 1. Is this the expected behavior, or should all components actually be
> [made] available before any routes are built? Should it be reported as a bug
> and/or an improvement?
>
> 2. I had worked around the issue by accessing the endpoint in Java code
> (getEndpoint("restlet")), how does it work there?
>
> 3. How exactly does the import in question fix the issue? [it worries me
> not to know if it ensures the component will be loaded before the route is
> started or just launches before it].
>
> Thanks,
>
> Fernando
>
> On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi Fernando,
>>
>> thanks for spotting that, it can help Camel/ServiceMix users :)
>>
>> Regards
>> JB
>>
>>
>> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>>
>>> Hello,
>>>
>>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>>> which I discussed at
>>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>>
>>> The fix was adding an OSGi reference manually to the beans.xml file,
>>> which
>>> was awkward because I expected all components, for example, to be loaded
>>> before any routes that use them to be started.
>>>
>>> If you prefer me to take this discussion to the ServiceMix mailing lists
>>> instead, please advise.
>>>
>>> Thanks,
>>>
>>> Fernando
>>>
>>>
>
>
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
I've created an issue at https://issues.apache.org/jira/browse/CAMEL-3517 for
this matter. Thanks.
On Thu, Jan 6, 2011 at 1:28 AM, Fernando Ribeiro <
webmaster@fernandoribeiro.eti.br> wrote:
> Can you please help with questions 1 and 3? Thanks.
>
>
> ---------- Forwarded message ----------
> From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
> Date: Wed, Jan 5, 2011 at 9:13 AM
> Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
> To: users@camel.apache.org
>
>
> JB,
>
> No problems, will actually blog about it next, just wanted to know if
> anyone here can help me with the following questions about the issue from
> the original discussion:
>
> 1. Is this the expected behavior, or should all components actually be
> [made] available before any routes are built? Should it be reported as a bug
> and/or an improvement?
>
> 2. I had worked around the issue by accessing the endpoint in Java code
> (getEndpoint("restlet")), how does it work there?
>
> 3. How exactly does the import in question fix the issue? [it worries me
> not to know if it ensures the component will be loaded before the route is
> started or just launches before it].
>
> Thanks,
>
> Fernando
>
> On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi Fernando,
>>
>> thanks for spotting that, it can help Camel/ServiceMix users :)
>>
>> Regards
>> JB
>>
>>
>> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>>
>>> Hello,
>>>
>>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>>> which I discussed at
>>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>>
>>> The fix was adding an OSGi reference manually to the beans.xml file,
>>> which
>>> was awkward because I expected all components, for example, to be loaded
>>> before any routes that use them to be started.
>>>
>>> If you prefer me to take this discussion to the ServiceMix mailing lists
>>> instead, please advise.
>>>
>>> Thanks,
>>>
>>> Fernando
>>>
>>>
>
>
Fwd: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
Can you please help with questions 1 and 3? Thanks.
---------- Forwarded message ----------
From: Fernando Ribeiro <we...@fernandoribeiro.eti.br>
Date: Wed, Jan 5, 2011 at 9:13 AM
Subject: Re: "Failed to resolve endpoint" on ServiceMix 4.2
To: users@camel.apache.org
JB,
No problems, will actually blog about it next, just wanted to know if anyone
here can help me with the following questions about the issue from the
original discussion:
1. Is this the expected behavior, or should all components actually be
[made] available before any routes are built? Should it be reported as a bug
and/or an improvement?
2. I had worked around the issue by accessing the endpoint in Java code
(getEndpoint("restlet")), how does it work there?
3. How exactly does the import in question fix the issue? [it worries me not
to know if it ensures the component will be loaded before the route is
started or just launches before it].
Thanks,
Fernando
On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi Fernando,
>
> thanks for spotting that, it can help Camel/ServiceMix users :)
>
> Regards
> JB
>
>
> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>
>> Hello,
>>
>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>> which I discussed at
>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>
>> The fix was adding an OSGi reference manually to the beans.xml file, which
>> was awkward because I expected all components, for example, to be loaded
>> before any routes that use them to be started.
>>
>> If you prefer me to take this discussion to the ServiceMix mailing lists
>> instead, please advise.
>>
>> Thanks,
>>
>> Fernando
>>
>>
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
JB,
No problems, will actually blog about it next, just wanted to know if anyone
here can help me with the following questions about the issue from the
original discussion:
1. Is this the expected behavior, or should all components actually be
[made] available before any routes are built? Should it be reported as a bug
and/or an improvement?
2. I had worked around the issue by accessing the endpoint in Java code
(getEndpoint("restlet")), how does it work there?
3. How exactly does the import in question fix the issue? [it worries me not
to know if it ensures the component will be loaded before the route is
started or just launches before it].
Thanks,
Fernando
On Wed, Jan 5, 2011 at 4:03 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi Fernando,
>
> thanks for spotting that, it can help Camel/ServiceMix users :)
>
> Regards
> JB
>
>
> On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
>
>> Hello,
>>
>> I've found an interesting issue when deploying a route in ServiceMix 4.2,
>> which I discussed at
>> http://fusesource.com/forums/thread.jspa?threadID=2493.
>>
>> The fix was adding an OSGi reference manually to the beans.xml file, which
>> was awkward because I expected all components, for example, to be loaded
>> before any routes that use them to be started.
>>
>> If you prefer me to take this discussion to the ServiceMix mailing lists
>> instead, please advise.
>>
>> Thanks,
>>
>> Fernando
>>
>>
Re: "Failed to resolve endpoint" on ServiceMix 4.2
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Fernando,
thanks for spotting that, it can help Camel/ServiceMix users :)
Regards
JB
On 01/04/2011 05:53 PM, Fernando Ribeiro wrote:
> Hello,
>
> I've found an interesting issue when deploying a route in ServiceMix 4.2,
> which I discussed at http://fusesource.com/forums/thread.jspa?threadID=2493.
>
> The fix was adding an OSGi reference manually to the beans.xml file, which
> was awkward because I expected all components, for example, to be loaded
> before any routes that use them to be started.
>
> If you prefer me to take this discussion to the ServiceMix mailing lists
> instead, please advise.
>
> Thanks,
>
> Fernando
>