User: jules_gosnell Date: 02/03/06 16:50:30 Modified: jetty FAQ Log: clarify a little (for Greg) Revision Changes Path 1.4 +12 -12 contrib/jetty/FAQ Index: FAQ =================================================================== RCS file: /cvsroot/jboss/contrib/jetty/FAQ,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- FAQ 6 Mar 2002 00:45:39 -0000 1.3 +++ FAQ 7 Mar 2002 00:50:30 -0000 1.4 @@ -3,8 +3,8 @@ ------------- A pure Java, HTTP1.1 httpd, Servlet 2.3 & JSP 1.2 WebContainer. In -short an elegant solution to serving static and dynamic web -content. See jetty.mortbay.org for more information. +short a 100% pure Java and elegant solution to serving static and +dynamic web content. See jetty.mortbay.org for more information. Why would I want to use Jetty instead of Tomcat/Catalina? @@ -99,7 +99,7 @@ Virtual hosts are an area currently not (AFAIK) addressed by the J2EE spec (1.3). There is an intention within the JBoss team to provide a -proprietary extension to provide this functionality. While this is +proprietary extension to encompass this functionality. While this is being worked out the interim solution is to go around JBoss and talk directly to Jetty via the jetty-web.xml file in your .war's WEB-INF directory. @@ -153,15 +153,15 @@ requests)it's HttpSessions are still made available to other instances of the same WebApp within the cluster. -This extension is problematic since J2EE requires that on stopping a -distributed WebApp should notify HttpSession attributes implementing -HttpSessionActivationListener before passivating/distributing -them. When the WebApp has been restarted and re-activates an -HttpSession the same attributes must be notifies again. If, because of -the reuse of this fn-ality to provide fail-over, attributes do not -receive passivation events on one node before receipt of activation -events on another, an asymmetry, which would not happen on a fully -compliant AppServer occurs. +This extension is problematic since J2EE requires that on being +undeployed, a distributed WebApp should notify HttpSession attributes +implementing HttpSessionActivationListener before +passivating/distributing them. When the WebApp has been re-deployed +and it re-activates an HttpSession the same attributes must be +notified again. If, because of the reuse of this fn-ality to provide +fail-over, attributes do not receive passivation events on one node +before receipt of activation events on another, an asymmetry, which +would not happen on a fully compliant AppServer occurs. Our integration allows the user to specify whether this extended behaviour (snapshotting) is required and, if so, exactly what
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
