Il 20/02/2014 15:03, Joakim Erdfelt ha scritto:
From the point of view of Jetty...
The webapp is started, which means it undergoes a series of
configuration steps (such as annotation scanning, jndi setup,
WEB-INF/web.xml loading, ServletContainerInitializer execution,
servlet init(), etc ...). Once the webapp startup is completed it is
available to receive requests per the servlet spec.
However, based on your experience, something is initializing outside
of these standard processes.
Thanks Joakim for the reply
In such a scenario, there is nothing jetty can do to determine if the
webapp is started and available to receive requests.
You are now in an app specific problem space, you'll need to
interrogate the app itself to determine if it is available for
requests or not.
Ok, understand
Thank you
--
Andrea Cappelli
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
