-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howard,
On 5/27/2010 8:01 PM, Howard Lewis Ship wrote:
> I believe my client is using Tomcat 6; I'll check.
>
> So, at startup, the Manager reads the saved HttpSession state into
> memory, then starts init'ing filters and servlets? I really need to
I believe my client is using Tomcat 6; I'll check.
So, at startup, the Manager reads the saved HttpSession state into
memory, then starts init'ing filters and servlets? I really need to
find a way to work on that ordering.
On Thu, May 27, 2010 at 8:43 AM, Pid wrote:
> On 27/05/2010 16:31, Howar
On 27/05/2010 19:08, Caldarale, Charles R wrote:
>> From: Pid [mailto:p...@pidster.com]
>> Subject: Re: Clustering, De-Serialization and Order of Operations
>>
>> Session persistence is a Manager Valve function
>
> Is that true even for the start() and stop()
> From: Pid [mailto:p...@pidster.com]
> Subject: Re: Clustering, De-Serialization and Order of Operations
>
> Session persistence is a Manager Valve function
Is that true even for the start() and stop() methods of StandardManager? I
thought valves came into play during request pro
package filters;
import java.io.*;
import java.sql.*;
import java.util.*;
import javax.servlet.*;
/**
* Example filter that dumps interesting state information about a request
* to the associated servlet context log file, before allowing the servlet
* to process the request in the usual wa
On 27/05/2010 16:31, Howard Lewis Ship wrote:
> I have a question, on behalf of a client, concerning Tomcat clustering
> and deserialization, in the context of a Tapestry 5 application.
>
> Here's the short form: some of the objects that a Tapestry
> application may put into the HttpSession will
