aspose file tools*
The moose likes Servlets and the fly likes Why init() if constructor is there Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » Servlets
Bookmark "Why init() if constructor is there" Watch "Why init() if constructor is there" New topic
Author

Why init() if constructor is there

Raj Kumar Bindal
Ranch Hand

Joined: Apr 15, 2006
Posts: 418
Why init is required if allmost all things i can do in my constructor of servlet.(i think only ServletConfig is not available in constructor).
Vince HW Chan
Greenhorn

Joined: Aug 16, 2005
Posts: 5
It is interesting, my guess is it may be,

Servlet, just like EJB, is supposed to be instantiated by container.
And, they are not supposed to " throw exception" while they are instantiated. If you have operation which may throw exception inside the constructor, it fails. Or, if you catch the exception within the consturctor, can you sure the servlet still "valid"?

However, init() declare to throw ServletException, which allow you to stop servce any requests if the setup operations throw excpetion or error occurs.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 61433
    
  67

Originally posted by Raj Kumar Bindal:
i think only ServletConfig is not available in constructor


You answered your own question.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
Charles Lyons
Author
Ranch Hand

Joined: Mar 27, 2003
Posts: 836
You answered your own question.

But that doesn't really answer it: why is there a separate init(ServletConfig) method? Why not just have a constructor with the ServletConfig parameter?

My guess is that it gives a clean set of lifecycle methods: the constructor is used for instantiation, the init method for initialisation. Perhaps also they thought they might add alternative init methods (with different parameters), and having extra constructors around would then just be cumbersome? I think the point raised about throwing exceptions is a good one.

But like many things in life, that was just the decision that was made and we learn to live with it... there's no point arguing, as now it's established it's never going to change!


Charles Lyons (SCJP 1.4, April 2003; SCJP 5, Dec 2006; SCWCD 1.4b, April 2004)
Author of OCEJWCD Study Companion for Oracle Exam 1Z0-899 (ISBN 0955160340 / Amazon Amazon UK )
Manesh Kumar
Ranch Hand

Joined: Mar 21, 2006
Posts: 94
Another way to look at this, though this might not be answer.

When servlets were first introduced, there were more Applet programmers. Just for maintaining coding style of Applet with servlet and easier switch over for Applet programmers(where they used init method for initialization), this could have been introduced for convenience to the java programmers.


Manesh
Jeroen T Wenting
Ranch Hand

Joined: Apr 21, 2006
Posts: 1847
Constructing a servlet instance is (or can be, I think it's up to the container to decide what to do) a 2 stage process.


42
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18669
    
    8

The other issue here is that specifying that a subclass must have a constructor with a particular signature is a design that can't be enforced. That's just one more thing to go wrong. Whereas an "init" method can be specified in the superclass, or the interface, and if subclasses need to override it they can. But if they don't override it, there is no problem either.
Neeraj Mariyana
Greenhorn

Joined: Jan 25, 2006
Posts: 1
I think it is because the Servlet is instantiated by the container using the Class.forName(<servlet class> .getInstance().
For it to do this the servlet should have a no argument constructor. Hence ServletConfig cannot be passed.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why init() if constructor is there