Fine,
There might be cases where it's hard to simulate the
webserver ( like redirects, or sessions ), but how
can I solve this problem of providing the OutputStream for the
ServletRequest ??? If we're using the WebServer's implementation
I don't see how it can be over-ridden (since it hasn't been
already).
Also, can we set up cactus to run as part of the build process ???
I'm trying to introduce UI developers in our company to junit
and extreme programming, and want to assure them that we definitely
can unit test their code. Does running under tomcat pre-empt this
from happenning ???
--- jerome
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 08, 2001 6:29 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Access to HttpServletRequest.getInputStream() in Cactus
>
>
>
>
> On Tue, 8 May 2001, Jerome Banks wrote:
>
> >
> > [snip]
> > Also, I don't quite understand why Cactus needs to be
> run inside a
> > WebServer like
> > Tomcat. Why can't one create concrete representations of
> > HttpServletRequest and
> > HttpServletResponse, and use that ??? Am I missing something ???
> >
>
> It's not just the request and response objects that matter. Just to
> continue using Struts as the example, it depends on a completely
> functional implementation of the ServletConfig, ServletContext,
> HttpSession, and RequestDispatcher APIs, plus a full
> implementation of JSP
> pages (including custom tag support). Pretty soon you end up writing
> your very own servlet container .... it's better to reuse
> what is already
> there.
>
> > thanks in advance ...
> > --- jerome
> >
> >
> >
>
> Craig
>
>
