Yes, this was a no-brainer. Did exactly the same thing. There is a lot
of dead code remaining though. 

Either you subclass and have inaccessible/unused methods lingering around 
or you copy the code into your own class and have to maintain this code
as the Slide code gets updated. There should be no *need* to subclass when
one is willing to start from scratch. Developers should have a choice.

The only thing that prevents people from writing their own servlet is this
little bugger:

public void init(ServletConfig config) throws ServletException {
        super.init(new WebdavServletConfig(config));
}


> -----Original Message-----
> From: Christopher Lenz [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, January 26, 2002 08:07
> To: Slide Users List
> Subject: Re: RE: Attn Developers -
> org.apache.slide.webdav.WebdavServletConfi g
> 
> 
> 24.01.2002 20:35:16, Frederic Kam-Thong <[EMAIL PROTECTED]> wrote:
> 
> >
> >FYI - So far, I've subclassed WebdavServlet and implemented a JSP
> >template-based directory browser but the bytecode could be leaner if 
> >I didn't subclass...
> 
> I've done pretty much the same thing half a year ago :)
> You'll *need* to subclass WebdavServlet to implement doGet(), 
> which should forward() to the JSP page(s).
> 




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to