Wars don't take part in the service life-cycle.
They also don't allow sub-deployments.
If you must put the classes in WEB-INF/lib,
you will have to start the scheduler manually
using a preloaded servlet init() method.
have done that this way before, but after a few deployments I had more than one scheduler runing. And more than on parallel scheduler could lead into database locks in my application....
With which deployment (ear, sar, etc.) format is the deployment of the -service possible?
All of them,
but for a ear, you need to explicity state it
NOTE: I think in 3.0 -service.xml wasn't included
as a nested deployment until recently.
But a nested sar will work.