no argument constructor in beans

[shawn peter]

why should there be a no argument constructor in beans?
can't there be a any overloaded costructor with no arg ones?

[Seetharaman Venkatasamy]

default constructor is must. useBean designed like that

[Shailesh Narkhede]

In Javabean specification mentioned that bean should have no arg constructor.

Here you get specification

[Bear Bibeault]

Please take the time to choose the correct forum for your posts. This forum is for questions on JSP.

For more information, please read this.

This post has been moved to a more appropriate forum.

[Ernest Friedman-Hill]

aruna sameera wrote:why should there be a no argument constructor in beans?
can't there be a any overloaded costructor with no arg ones?

Yes, you can have as many overloaded constructors as you'd like. But many JavaBeans tools (like the JSP "useBean" tag already mentioned) expect to be able to create a JavaBean using only the name of the class -- i.e., they'll call

Object bean = Class.forName(theClassName).newInstance();

For this to work, there must be a no-argument constructor. If you give your class other constructors, then you can use those constructors explicitly in your code. But tools will always use the no-argument one.