Page History

...

1. The ServiceMix container reads the servicemix.xml file and sees it needs to instantiate a filePoller FilePoller
2. The container calls the init method of filePoller FilePoller as well as the init methods of its parents
3. The container determines that filePoller FilePoller is an MBean and, therefore, calls the "start" method of filePoller FilePoller, which it inherits from its parent PollingComponentSupport
4. 5. Analyzing the The start method , the start method will:
   a. Create a timerTask, which overrides the "run()" method inline, the run() method will eventually get the WorkManager and schedule work
   b. Start method uses the "timer" (created in the init method) to schedule the timerTask it just created at a fixed rate, timer.scheduleAtFixedRate(timerTask, firstTime, period)
   c. Timer will call the run method of the timerTask periodically
   d. timerTask's run method is defined inline.
   e. it will get the workManager object (see below for details)
   f. the work manager will call scheduleWork(PollingComponentSupport.this). note: it passes in PollingComponent support, which by virtual of its inheritance hierarchy, is also of type "Work", which is also a "runnable"
   g. WorkManager.scheduleWork(Work) will likely create or get a Thread, passing in a runnable, i.e. PollingComponentSupport, and call its "run" method
   h. PollingComponent's run method calls poll(), which is implemented in filePoller
   i. From this point on the call sequence can be followed in filePoller
   6. The start method of PollingComponentSupport, will eventually call super.start(), which propagates up to call the start method of BaseLifeCycle, which sets the component state to RUNNING

...