Just for a differing point of view, I find htmlunit easier to use than 
httpunit.
--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au


"James Childers" <[EMAIL PROTECTED]> wrote on 15/12/2002 04:33:08 AM:

> Leos,
> 
> > My problem is, that there is no single line in documentation
> > describing, how to open URL with jsp. Doc for ServletTestCase
> > relies on fact, that you are instantiating servlet class,
> > which will not work with jsp. And JspTestCase seems to me
> > focused on tag library, and there is no way to execute jsp.
> 
> From what you have described you are looking for a functional test 
> environment, not a unit test environment. HTTPUnit might be more in 
> line with your requirements. Cactus is designed to test the 
> components of a web application --  mostly servlets, filters, tags. 
> If you are just wanting to test that a JSP gets executed/built 
> properly, use HTTPUnit. 
> 
> What you have described, however, suggests that you have at least 
> some business logic in your view (JSP) and might want to consider 
> moving that functionality up the hierarchy a bit. 
> 
> As far as your needs are concerned, read the following for more info:
> 
> http://jakarta.apache.org/cactus/mockobjects.html
> 
> -= J
> 
> 
> 
> 
> --
> To unsubscribe, e-mail: 
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
> 

> ForwardSourceID:NT00099A8E