Russell Gold wrote:
>
> At 06:54 PM 7/2/2001 +0100, Jari Worsley wrote:
> >Russell Gold wrote:
> > >
> > > At 06:07 PM 6/29/2001 +0100, Jari Worsley wrote:
> > > >- by making HttpWebResponse public, you can give it nonsense for the
> > > >target and URL (1st and 2nd params), then give it the HttpURLConnection,
> > > >and get back an HttpWebResponse object, allowing calls like getText(),
> > > >getForms(), etc...
> > >
> > > Or we can specialize it to make a CactusWebResponse - it would be cleaner
> > > and shouldn't take a lot of work.
as HttpWebResponse has "default" scope, then to extend and create a
CactusWebResponse would mean one of two things, either create the
CactusWebResponse in the com.meterware.httpunit package, or change the
scope of the class and sole constructor to public or protected. If
protected then we could write CactusWebResponse in a cactus package
rather than introducing a dependency into your source (bad!).
Jari
--
Jari Worsley
Senior Programmer
Hyperlink Interactive Ltd
