Hi Jules > 1. Are you sure that JSR77 talks at the granularity of Servlets - or is > it WebApplications - or both. A Servlet is not the unit of deployment, > the WebApplication is. A WebApplication may contain 0-n Servlets.
JSR-77 have an application (EAR) with one or more modules (WAR,JAR,RAR) and each containing eithe EJBs, Servlets or ResourceAdaptors. So, yes, JSR-77 needs both the web application and the servlets its contains. > 2. Jetty has a concept of deploy, start, stop and undeploy. Currently > webapps are started as soon as they are deployed - so when you say > start/stop, do you mean deploy/undeploy or start/stop ? JSR-77 is not clear in this point but the lack of the creation of services I think it means to start/stop but not deploy/undeploy. BTW what does start/stop mean (make it available/unavailable to serve) ? What happens with the servlets at this time. Can you start/stop servlets ? > 3. I am keen for Jetty to support a restart() and a redeploy() - atomic > functions which put incoming requests on hold while they do their job - > thus ensuring 24*7 service, with no lost requests, even if you upgrade > your website at a peak time... I believe JSR77 also has optional? > provision for (at least one of) these. I think that it is important that > we support it from the start even if it is simply implemented in terms > of the others... Ahhmm, where did you see that in JSR-77 ? Thanx - Andy ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
