5 comments

What is differ POJO from JavaBeans?

A big amount of hype from the side of Injection/IoC/Aspect zealots.
Now add to this also some serious VC founding in the last time, and you have the big picture :).

Ahmed.

0

Yeah, it's true that POJO as a term has been hyped.
Yet IMHO there's also a technical difference:
A JavaBean has properties (fields, getters, setters).
OTOH a business component may be implemented as a POJO in form of an EJB 3.0
stateless session bean, but it will not be a JavaBean because it offers
bussiness processing methods in its interface instead of JavaBean-style properties.

Yura wrote:

What is differ POJO from JavaBeans?

0

A JavaBean has private properties accessed via getters/setters and has an empty constructor. A POJO is usually very similar, but can be ANY java class, without any requirement for who it inherits from and with no particular constructor requirements (e.g. any java class).

0

The getters/setter also must follow the JavaBean naming convention, right?

"Norris Shelton" <no_reply@jetbrains.com> wrote in message
news:16880173.1180113609315.JavaMail.itn@is.intellij.net...
>A JavaBean has private properties accessed via getters/setters and has an
>empty constructor. A POJO is usually very similar, but can be ANY java
>class, without any requirement for who it inherits from and with no
>particular constructor requirements (e.g. any java class).


0

Please sign in to leave a comment.