LiveSite is essentially one large and fairly complex servlet filter. If the request is not one that LiveSite handles (i.e. extension isn't .page or .site or .sitemap or .alias and doesn't match any alias in the sitemap), then the request is allowed to "flow through" to the servlet container. Since the servlet container has no actual servlets defined, it renders all other assets (.js, .css, .html, and .jsp) natively.So, yes you can use the same servlet container to render JSPs. However, you cannot have LiveSite inspect or alter a request for a JSP in any way. That means, you can't have a JSP run a precontroller in LiveSite for example. The only thing that is shared between the two is the native Java session object, meaning that context.getRequest.getSession() in LiveSite returns the same object as request.getSession() in a JSP. That means if your controllers/externals save stuff in the session, that same stuff is accessible to your JSP. The classpath is also identical on both sides, so any custom classes you put in livesite-customer.jar (or another custom JAR) is available to both LiveSite and your JSP.
