why public constructor should be provided in javabean class

Question

I heared rules of JavaBean, in which first and main rule is , for every JavaBean class explicitly programmer should provide public default constructor . Please can anyone explain why do we need to provide default constructor for JavaBean

UPDATE :

Please explain clearly, why jvm will not provide default constructor for JavaBeans and how jvm reacts on providing default constructor

Question already exsists. http://stackoverflow.com/q/2291856/713414 — Jayy, Feb 22 '12 at 12:03

Don Roby · Accepted Answer · 2012-02-22T12:42:33.747

I heared rules of JavaBean, in which first and main rule is , for every JavaBean class explicitly programmer should provide public default constructor . Please can anyone explain why do we need to provide default constructor for JavaBean

JavaBean instances are created by reflective calls to the no-arg constructor. So there has to be such a constructor.

Please explain clearly, why jvm will not provide default constructor for JavaBeans and how jvm reacts on providing default constructor

The jvm will provide a default constructor for a JavaBean if you have explicitly provided no constructors. If you do provide a constructor, you must provide a no-arg constructor besides any that you define with parameters.

score 1 · Answer 2 · answered Feb 22 '12 at 12:06

1

We might add some other contructors to our bean which take parameters, and if we have not included Default constructor in our class, other constructor would shadow it, thus making it not a valid bean anymore.

answered Feb 22 '12 at 12:06

reederz

983
1
12
29

score 0 · Answer 3 · answered Feb 22 '12 at 12:05

0

In my experience it is to prevent the situation where someone adds a constructor with parameters, and thus effectively removes the default constructor. By implementing the default constructor explicitly that is more unlikely to happen.

answered Feb 22 '12 at 12:05

Johannes

763
3
7

unless you call argumented constructor , jvm never call argumented constructor, even though argumented constructor is defined in class – developer Feb 22 '12 at 12:22

score 0 · Answer 4 · edited Feb 22 '12 at 14:10

0

This what wikipedaia says Java Bean Wikipedia article

The class must have a public default constructor (no-argument). This allows easy instantiation within editing and activation frameworks.

Actually it is esay to instanciate a class by introspection if it gets a default constructor

 getClass().getClassLoader().loadClass("mypackage.myclass").newInstance();

edited Feb 22 '12 at 14:10

developer

9,116
29
91
150

answered Feb 22 '12 at 12:07

diodfr

99
3

-1 it is not exact answer, please check , i have updated the question. – developer Feb 22 '12 at 12:20

score 0 · Answer 5 · answered Feb 22 '12 at 14:06

I suspect this is a misunderstanding of the difference between syntax and the generated class.

public class Alpha {
}

public class Beta {
  public Beta() {}
}

In Alpha the default constructor is implicit; in Beta it is explicit. Both have default public constructors as per the JavaBean spec.

public class Gamma {
  private final Type t;
  public Gamma(Type t) {
    this.t = t;
  }
}

On the other hand, Gamma does not meet the requirement as there is no public no-args constructor. There would be no way to instantiate this object without context about how to populate the constructor.

why public constructor should be provided in javabean class

5 Answers5