Checked in an initial version working with Jetty Continuations. It was necessary to modify the
ResponseState.block() API so that the request would be available to the continuation when the blocking
occurs.
svn commit . -m "Initial Jetty Continuation implementation along with more explicit exception handling
in BlockingServlet (ICE-1010)"
Sending src/com/icesoft/faces/webapp/xmlhttp/BlockingResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/BlockingServlet.java
Adding src/com/icesoft/faces/webapp/xmlhttp/ContinuationResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/PortletBlockingResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/ResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/ResponseStateManager.java
Adding src/com/icesoft/faces/webapp/xmlhttp/SessionExpiredException.java
Committed revision 12196.
Configure Jetty to allow idle HTTP connections: in etc/jetty.xml set maxIdleTime to 600000.
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.nio.SelectChannelConnector">
<Set name="port"><SystemProperty name="jetty.port" default="8080"/></Set>
<Set name="maxIdleTime">600000</Set>
<Set name="Acceptors">2</Set>
<Set name="confidentialPort">8443</Set>
</New>
</Arg>
</Call>
jetty-util-6.0.1.jar was added as a compile-time dependency. This appears to be apache-licensed,
but that needs to be confirmed. For ICEfaces we may just want to include the Jetty interfaces
rather than the entire jar (100k).
Since the exception handling in BlockingServlet is updated, we need to carefully add in the desired
handling. The previous "catch(Exception e)" was too broad, but we will temporarily encounter errors
until we refine the handling to the exact exceptions needed.
Checked in an initial version working with Jetty Continuations. It was necessary to modify the
ResponseState.block() API so that the request would be available to the continuation when the blocking
occurs.
svn commit . -m "Initial Jetty Continuation implementation along with more explicit exception handling
in BlockingServlet (
ICE-1010)"Sending src/com/icesoft/faces/webapp/xmlhttp/BlockingResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/BlockingServlet.java
Adding src/com/icesoft/faces/webapp/xmlhttp/ContinuationResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/PortletBlockingResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/ResponseState.java
Sending src/com/icesoft/faces/webapp/xmlhttp/ResponseStateManager.java
Adding src/com/icesoft/faces/webapp/xmlhttp/SessionExpiredException.java
Committed revision 12196.
Configure Jetty to allow idle HTTP connections: in etc/jetty.xml set maxIdleTime to 600000.
<Call name="addConnector">
<Arg>
<New class="org.mortbay.jetty.nio.SelectChannelConnector">
<Set name="port"><SystemProperty name="jetty.port" default="8080"/></Set>
<Set name="maxIdleTime">600000</Set>
<Set name="Acceptors">2</Set>
<Set name="confidentialPort">8443</Set>
</New>
</Arg>
</Call>
jetty-util-6.0.1.jar was added as a compile-time dependency. This appears to be apache-licensed,
but that needs to be confirmed. For ICEfaces we may just want to include the Jetty interfaces
rather than the entire jar (100k).
Since the exception handling in BlockingServlet is updated, we need to carefully add in the desired
handling. The previous "catch(Exception e)" was too broad, but we will temporarily encounter errors
until we refine the handling to the exact exceptions needed.