Hello,
we're creating a session-scoped webservice with "Connection"-classes
that provide the methods for SOAP. These "Connection"-classes take the
Soap-Calls and pass them to our singleton-controller.
So far so good.
The problem is, that starting up the controller and the underlying model
takes a little time, so that we want to start it up right after
deploying it and before the first calls come in.
Currently we deploy the service and nothing get's started until the
first SOAP-Call is coming in. This first call let's axis create a
Connection-class which fecthes (and therefore creates) the controller
and the underlying model.
So: is there a way to start up the Controller before the first
SOAP-Calls come in? I spent quite some time now with searching but
couldn't find the right stuff. :-/
Greetings,
Franz