I'm a newbie to beans too.
I second Frank's question:
A database query can be a component too. How does a graphical property
editor deal with it?
Frank Fredstone =EDrta:
> mei <mei@[EMAIL PROTECTED]
> writes:
>
> > Sorry to interfere in this thread, but i've been confused by this
post.
> > It seems to me that you distinguish java beans and beans.
> > So the beans are those cl***** that complies to the setters and
> > getters stuffs... So now, what are the javabean? In particular, in
> > your example, what happens exactly when you set "Java-Bean" property
> > to true?
> > Thanks.
>
> Aside from indicating that the main class in the jar file is a java
> bean, I'm not sure. Maybe that is how the environment that gives you
> an interface (e.g. GUI) to bean customizers, determines which cl*****
> to present as components.
>
> I am also confused about javabeans. A javabean is not "a class with
> getters and setters". A javabean is a java component that can be
> designed to reveal information about itself, such as what component
> properties are accessible.
>
> A javabean component can be setup to be customizable in a property
> editor.
>
> What I don't understand though, is how a customized javabean is then
used=
.. In:
>
> http://java.sun.com/docs/books/tutorial/javabeans/index.html
>
> a lot is described, but not how a customized bean would be used from
> an application.
>
> In the tutorial the application making use of the component model is
> the NetBeans IDE, where NetBeans presents a GUI to a property editor
> and allows components to be associated with each other.
>
> It would clear things up for me if I could see an example of a non-GUI
> application making use of non-GUI components that have been customized
> in a property editor.
|
