Hi Matt,
This is an interesting observation. Are you sure your component has
really be activated ? For example, if your component happens to be
delayed (which is e.g. the case if the immediate attribute is set to
false or if the immediate attribute is not set at all and a service is
declared), the activate method is only called when the service provided
by the component is first retrieved.
Can you provide us with your component declaration for this case ?
Regards
Felix
Streeton, Matt schrieb:
I am new at using declarative services to create components and have those
components activated by the SCR. In order to keep my activate functions
brief, I spawn a thread from one of my component¹s activate method (which
has some time consuming processes). For some reason, that thread doesn¹t
seem to actually start until I interact with the Felix console. For example,
Felix starts up, all the bundles are started and activated properly. I don¹t
see the thread activity, however, until I hit the enter key inside the Felix
console. Is there any reason a thread wouldn¹t actually start on its own?
For clarification, I have included my activate method for my component
(which implements Runnable):
protected void activate(ComponentContext ctxt)
{
componentContext = ctxt;
thisThread = new Thread(this);
thisThread.start();
}
Thanks for any help, this has been puzzling!
- Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
