I'm not happy with the other answers, though they are not really
incorrect. (The object with a hashmap of properties thing that Hari
mentions is not really a JavaBean, though some packages can use maps
as if they were implicitly a JavaBean).
I'd rather explain it from a minimalist point of view.
I have no idea what a bean class is.
Bean class is an old name for awhat we call not a POJO.
Android essentially leaves only the PropertyChangeEvent, from the old
java.beans package.
On 23 янв, 02:50, TreKing treking...@gmail.com wrote:
On Sat, Jan 22, 2011 at 1:26 AM, Deeps
Hi Hari.
Just my two cents but if you mean
the Java Bean specification, then the spec is
a J2SE technology (
http://www.oracle.com/technetwork/java/javase/documentation/spec-136004.html
)
and comes into world long before the people start to thinking in terms
of EJBs and so on. Good luck ! Frank
Bean class is a pojo. You have private instance variables, with public
get/set methods. A property is an instance field with a get/set method. I
forget though if you need both.. there are some cases where you may want to
make a mutable property by using a constructor to set it, then only have a
On Jan 22, 7:50 pm, TreKing treking...@gmail.com wrote:
I have no idea what a bean class is.
It's one of those J2EE things that they shove at you in
diploma-mill university IT classes. Basically, an object
with a hashmap of properties, so that it's trivial to make
GUI front-ends that can
5 matches
Mail list logo
