Re: Java Bean Question
Chris ( Val ) wrote:
Actually, I just had a quick look on their tutorials, and even though
these are *not enterprise tutorials*, I found the following:
======== BEGIN ========
JavaBeans Design Issues
JavaBeans objects are like other user-defined data
types, but with the following additional options
Key word: "options".
that make the objects more useful:
Providing a public no-argument constructor
Nothing here about it being explicit.
Implementing java.io.Serializable
This directly contradicts the specification document.
Following JavaBeans design patterns
Set/get methods for properties
Add/remove methods for events
Java event model (as introduced by JDK 1.1)
Being thread safe/security conscious
Can run in an applet, application, servlet, ...
For an IDE to instantiate a bean, the class
implementation must provide a no-argument constructor.
Nothing about being explicit.
I hope that you can see why I have been confused over
these issues.
It is difficult sometimes, when information is fragmented over multiple
sources like this. Here is one place where they say, "Beans must provide a
no-argument constructor", and over there another place where they tell you
that you can do so implicitly, but don't mention Beans. This business of
integrating information from wildly disparate sources is among the strongest
learning skills a developer can have.
I am always feeling overwhelmed by the abundance of information I have to
assimilate to do work in this field, and not just in the Java universe.
--
Lew