In computing software, POJO is an acronym for Plain Old Java Object. The name is used to emphasize that a given object is an ordinary Java Object, not a special object, and in particular not an Enterprise JavaBean. The term was coined by Martin Fowler, Rebecca Parsons and Josh MacKenzie in September 2000:

"We wondered why people were so against using regular objects in their systems and concluded that it was because simple objects lacked a fancy name. So we gave them one, and it's caught on very nicely."^[1]

The term "POJO" is mainly used to denote a Java object which does not follow any of the major Java object models, conventions, or frameworks such as EJB. The term continues the pattern of older terms for technologies that do not use fancy new features, such as POTS (Plain Old Telephone Service) in telephony, and PODS (Plain Old Data Structures) that are defined in C++ but use only C language features, and POD (Plain Old Documentation) in Perl. The equivalent to POJO on the .NET framework is Plain Old CLR Object.

Contents 1 POJO generation projects 2 Pojo Testing Projects 3 See also 4 References

POJO generation projects

Roma Meta Framework 

DDD centric framework. The innovative holistic approach lets the designer/developer to view anything as a POJO: GUI, I18N, Persistence, etc.

OpenXava 

Framework to develop J2EE business applications rapidly and easily. It's based in business components defined with XML. Feature rich and flexible since it's used for years to create business applications. Generates POJO Hibernate EJB2 and EJB3 JPA ...

PlainXML 

Generating POJO by DTD; XML-POJO mapping via Java5 annotations or DTD; XML manipulations using POJO without SAX/DOM; Preprocessing of XML documents using expression language; Binary XML; RMI friendly XML; Exporting to JSON; XML marshall/unmarshall ...

PAT 

AOP (JBossAOP) persistence library (aspect library). Provides persistence layer with underlying Prevayler (1.02). Allows users to write their code without worrying about persistence code (POJO). Uses annotations.

Java O/RM 

This is a Java Object Relational mapping tool that is very simple to use. It works with all major databases and requires only minimal coding effort. JOR strictly follows the POJO / POJI (Plain Old Java Objects / Plain Old Java Interfaces) model.

AutoPersistJ 

This project aims to assist developers in developing java EE persistence layer for existing database tables. It gets metadata of selected database tables and generates classes for them. it uses and extends the ideas of DbGen project to EJB 3.0 POJO.

PojoGen

It is a small tool to generate Java Code (a POJO) for an APPFUSE-based project from a DDL file, which is created from an ER diagram by Microsoft VISIO. It makes an APPFUSE-based project more easy to use.

Pojodbc

An easy-to-use Java Object Relation mapping library without configurations file or annotations. Built on top of JDBC, you still use your optimized native SQL and get POJOs.

Apache Felix iPOJO 

A new type of dynamic service-oriented component runtime that runs pure POJO applications on the top of OSGi platforms. Non-functional (extra-functional) services can be added and removed at runtime.

JBoss Microcontainer

The JBoss Microcontainer is a refactoring of JBoss's JMX Microkernel to support direct POJO deployment and standalone use outside the JBoss application server.

Naked Objects

An open source framework that auto-creates an object-oriented user interface from POJOs using the naked objects pattern.

Metawidget

A 'smart User Interface widget' that populates itself, at runtime, with UI components to match the properties of POJOs.

fbDaoGenerator

Fbdaogenerator connects to a Firebird Database, reads the metadata of the Database by querying the system-tables, and generates POJOs and Data Access Objects.

Pojo Testing Projects

• OpenPojo a pluggable testing framework

See also

• Data Transfer Object
• Anemic Domain Model

References