Naveen Malik

• Jul 8th, 2006

 

The original reason for init() was that ancient versions of Java couldn?t dynamically invoke constructors with arguments, so there was no way to give the constructur a ServletConfig. That no longer applies, but servlet containers still will only call your no-arg constructor. So you won?t have access to a ServletConfig or ServletContext.

javadeep

 Profile Answers by javadeep Questions by javadeep

• Jul 8th, 2006

 

what about reflection api. i think reflection is there from begining to invoke constructors with args also.

Ramu Kondapalli

• Jul 19th, 2006

 

Servlet life cycle is mannaged by the servlet container not the JVM.

According to servlet specification the servlet container calls init() method of servlet, not the servlet constractors. At this point the constructor is called the class is not really a Servlet.

Because the servlet container manages the servlet lifecycle, one should never call the constructor, the init and destroy methods.

sunil

• Aug 10th, 2006

 

If u used a constuctor then no probs it's working fine but u cant used servletconfig and u cant passed argument constructor b'coz only first time yr constructor has called and for other request directlly service method called  so we cant able to use  initilization paramter for that reason we r avoid constructor