what is the use of using constructors in servlets as we have init method for initialization purpose?

All servlets have a default no-args constructor, which gets called before the init(...) method. The Servlet container can't know what sort of parameters you're expecting as part of the servlet-instance construction step, so it has to assume you have a no-arg constructor that's available to create a "default" instance of the servlet.

Cheers

Martyn

If we write only a constructor with arguments in our servlet, the servlet container will be unable to instantiate our servlet. Is there any way to enforce the user not to write an argumented constructor??

Regards,
Sunil Phani Manne

Many of life's failures are of people who did not realize how close
they were to success when they gave up.       &nbsp ;        & nbsp;       
        &n bsp;       &nbs p;       - Thomas Edison

:D:D

As u know by defaultjava gives a no argument constructor for every class. but if u provide a constuctor java will not give u the default constructor. In such a case u should provide one. Here when a servlet is instantiated the servlet container will call its no-arg constructor which is not present coz u have given an argument constructor. so the only option is u have to givea no arg constructor explicitly if u have given any other constructor for the servlet. Hope u have got my point. Thank You.
rgds Jiji

You could forbid users from extending javax.servlet.http.HttpServlet, and instead require them to extend an HttpServlet instance you have designed. Design your instance to have a public no-arg constructor -- this way there's always a no-arg constructor.

Jon Emerson
http://images.burningman.com/index.cgi?q_photog=emerson