Why pojo

Computer Graphics. Software Engineering. Web Technology. Cyber Security. C Programming. Control System. Data Mining. Data Warehouse. Javatpoint Services JavaTpoint offers too many high quality services. Example: POJO class is used to define the object entities. It must have a public default constructor.

It may have the arguments constructor. All objects must have some public Getters and Setters to access the object values by other Java Programs. But, all instance variables should be private for improved security of the project. A POJO class should not extend predefined classes.

It should not implement prespecified interfaces. It should not have any prespecified annotation. Below is the working of the POJO class. Java Bean Java Bean class is also an object class that encapsulates several objects into a single file Bean Class File. Both properties should be private to have complete control of fields.

Properties must have the getters and setter to access them in other Java programs. The POJO is used when we want to provide full access to users and restrict our members. And, the Bean is used when we want to provide partial access to the members. Connect and share knowledge within a single location that is structured and easy to search. In my opinion , calling getters and setters is slower than direct access to a field. The name is used to emphasize that a given object is an ordinary Java Object, not a special object.

A POJO is usually simple so won't depend on other libraries, interfaces or annotations. This increases the chance that this can be reused in multiple project types web, desktop, console etc. As someone has already pointed out in the comments, your object is technically a POJO already however you have specifically asked about getters and setters which are more akin to JavaBeans.

Yes, accessing or setting the values via method calls may be slower than direct field access but the difference is barely noticeable and it certainly won't be the bottleneck in your program. Whilst the advantages are clear this does not mean that getters and setters are a silver bullet.

There are a number of 'gotchas' to consider when designing real world, robust scalable classes. This answer to a very similar question looks at some considerations in detail when designing a class that has getters and setters.

Although the suggestions may be more relevant depending on the type of class you are designing E. Also note that there may be certain scenarios where a class with direct field may be advantageous such as when speed is essential or memory is limited although this should only be considered after profiling your code and finding that it is actually a bottleneck. Also be careful that you are not just wrapping all of your fields in getters and setters as this is really missing the point of encapsulation.

This answer provides a good summary of the reasons for choosing a POJO over a JavaBean style object with getters and setters. Getters and setters, especially the simplest forms will just be inlined by the JIT compiler and thus remove the method call overhead. This sounds very much like premature optimisation. If you ever get a bottleneck, then profile and look where it occurs. I am fairly certain it'll be not in property accesses.

In this Joshua Bloch says there is nothing inheriently wrong with public fields in package-private or nested classes but strongly advises against use public classes.

Imagine if some other programmer is using your code. If you don't provide setter and getter methods then he can directly call your variable and it surely will affect to your code.

And it may lead to security issues So by providing POJO class you are forcing him to call on your methods rather than directly calling your Instance variables. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. They were introduced in EJB 3. Attention reader! Get hold of all the important Java Foundation and Collections concepts with the Fundamentals of Java and Java Collections Course at a student-friendly price and become industry ready.

Implement prespecified interfaces, Ex: public class Bar implements javax. Contain prespecified annotations, Ex: javax. POJOs basically defines an entity. As you can see, there is no restriction on access-modifiers of fields.

They can be private, default, protected, or the public. It is also not necessary to include any constructor in it. Following image shows a working example of POJO class.

Controllers interact with your business logic which in turn interact with POJO to access the database. In this example a database entity is represented by POJO. This POJO has the same members as database entity. Java Beans Beans are special type of Pojos. There are some restrictions on POJO to be a bean.

Serializable i. Fields should be private. This is to provide the complete control on fields. Fields should have getters or setters or both. A no-arg constructor should be there in a bean. Fields are accessed only by constructor or getter setters.