| Delegates requests to a WebServiceContainer which is presumably for a POJO WebService
Nothing stopping us from using this for EJBs or other types of webservices other than
it is more than we need. EJB webservices use the JettyEJBWebServiceContext.
From a 10,000 foot view the Jetty architecture has:
Container -> Context -> Holder -> Servlet
A Container has multiple Contexts, typically webapps
A Context provides the JNDI, TX, and Security for the webapp and has many Holders
A Holder simply wraps each Servlet
The POJO Web Service architecture on Jetty looks like this:
Container -> WebApp Context -> JettyPOJOWebServiceHolder -> POJOWebServiceServlet
The EJB Web Service architecure, on the other hand, creates one Context for each EJB:
Container -> JettyEJBWebServiceContext
version: $Rev: 476049 $ $Date: 2006-11-16 20:35:17 -0800 (Thu, 16 Nov 2006) $ |