The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

Jacobdeiter (2) [Avatar] Offline
#1
Hi all

Can any one explain what is pojo specification ,Java bean specification and difference between them
simbo1905 (30) [Avatar] Offline
#2
Re: Pojo and Javabean specification
I don't believe that there is a pojo specification. The word was just a "sexy name" that was made up to describe regular java objects rather than EJB1 or EJB2 code. The Java Bean specification is of course a specification. It creates objects which expose their internal data structures. Originally that was intended to let tools such as IDEs be able to reject on 3rd parth configurable objects to be able to present a generic UI to let people set the properties of the objects. JMX is the J2EE standard which has the same purpose for container managed code.

There is a school of thought which says that exposing all of the fields of you objects is a violation of encapsulation and so poor OO design. Some people insist that you copy your domain objects into DTOs and back again to talk to clients. That seems to conflict with the PiA book. This matter is discussed at the following post:

http://www.manning-sandbox.com/thread.jspa?threadID=34550&tstart=0