Hi Kazuhito, That looks cool thanks. Are you sure this is not causing any trouble in any servlet container? I'm asking because I'm not sure the spec allows creating threads. I know it works in some cases (I also tried this a few years back) but I'd like to know the limitations of creating a thread in a servlet container.
Dave, what do you think? Thanks -Vincent > -----Original Message----- > From: Kazuhito SUGURI [mailto:[EMAIL PROTECTED] > Sent: 05 February 2004 12:52 > To: [EMAIL PROTECTED] > Subject: Re: Browser/Web Server timeout when accessing ServletTestRunner > for long tests > > Hi Vincent and Dave, > > Sorry, I had take mistake. > > In article <[EMAIL PROTECTED]>, > Tue, 3 Feb 2004 16:30:47 +1200, > [EMAIL PROTECTED] wrote: > dsearle> 2 Modify Servlet Test Runner (or create a new runner) that can > run in a > dsearle> asynchronous mode. > dsearle> This would involve spawning a thread to run the actual test and > storing the > dsearle> TestResult somewhere (e.g. ServletContext) with an ID. > dsearle> The browser could then reload the page (automatically if > required) with an ID > dsearle> for the TestResult. My only concern with this approach is any > threading issues? > > I wrote such kind of Servlet Test Runner before, and find it. > I don't use this Servlet Test Runner because I decided to not use browser > interface. So, the classes are not maintaind for a long time. > However, I think this is good enough for the stat point. > > Regards, > ---- > Kazuhito SUGURI > mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
