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 <
webmas...@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é <j...@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
>>>
>>>
>
