Proper injection usage in AnotherSimpleJob class
[TORQUE-257] Provide support for 'at' jobs

Added suport for new way of scheduling jobs:

The job will be executed every 200 ms, from now, for the next 10 seconds
TorqueBox::ScheduledJob.at('SimpleJob', :every => 200, :until => Time.now + 10)

The job will be executed for the first time in 10 seconds (current time + 10 seconds), then every 500 ms, for the next 10 seconds (current time + 20 seconds)
TorqueBox::ScheduledJob.at('SimpleJob', :at => Time.now + 10, :every => 500, :until => Time.now + 20)

The job will be executed for the first time in 5s and repeated 3 times. The time between executions is set to 1.5s
TorqueBox::ScheduledJob.at('SimpleJob', :in => 5000, :repeat => 3, :every => 1500)

Added integration tests and documentation.
null injections means null injection string
Merge remote-tracking branch 'goldmann/TORQUE-257-at-jobs'
Revert "Proper injection usage in AnotherSimpleJob class"

This reverts commit ef91514c3f0e2bab94c8f05fbf6fb7a235e5df67.
Be a bit looser on the at_job integ expected counts
Revert "Be a bit looser on the at_job integ expected counts"

This reverts commit b35cf5a7981c38cd90bf116a00df7414ee8153e4.
Make sure we schedule the job after the component resolver is added to the scheduler
Change all doc and example references of fetch to TorqueBox.fetch (TORQUE-1056)
Allow to set the 'stopped' parameter for jobs and message processors
both in yaml and Ruby deployment descriptors. By default 'stopped' is set
to false.
Use a thread pool to executing all blocking MSC start methods (TORQUE-1055)
[TORQUE-860] Allow to deploy Message Processors and Jobs stopped

Allows to deploy message processors and jobs stopped. This feature will
make it possible to start jobs and message processors but not to run
them at application boot time.

Three new methods were exposed for message processor management: start,
stop and started?.

This commit includes integration tests.
Added docs for TORQUE-860
Merge pull request #149 from goldmann/TORQUE-860-mp-and-jobs-deploy-stopped

[TORQUE-860] Allow to deploy Message Processors and Jobs stopped
minor grammar
Try to make messaging_spec a bit more resilient on slow machines
Use of CountDownLatch instead of ExecutorCompletionService. This makes
watching for the service installation/removal easy.

Documentation for the ScheduledJob class and JobSchedulizer was
extended.

Removed the "should timeout" integ since it doesn't make sense after
removing the :wait option. The timeout is set now to 30s in
JobSchedulizer.

Fixed manual after removing the :wait option.