Simplify Old Java Objects / News: Recent posts

SOJO version 1.0.0 is released

after a long time and many bug fixes I have released SOJO version 1.0.0

Posted by Mario Linke 2009-05-04

SOJO version 1.0 work in progress

I will fix all known bugs and then release verion 1.0.
You can help and send bugs or feature request.

Posted by Mario Linke 2008-03-19

SOJO release version 0.5.0

The Open Source project Sojo has announced the next release (version 0.5.0).
The intention for this project is a Java framework, that convert JavaBeans in a simplified representation .
So it is easy and uniformly to handle and control the access to JavaBeans properties.
This framework want to complement POJOs, where Java communicate with "other worlds. Other worlds are interfaces,
where object orientation is not supported or is not the best decision.... read more

Posted by Mario Linke 2007-05-01

SOJO release version 0.4.0

The Open Source project Sojo has announced the next release (version 0.4.0).
The intention for this project is a Java framework, that convert JavaBeans in a simplified representation .
So it is easy and uniformly to handle and control the access to JavaBeans properties.
This framework want to complement POJOs, where Java communicate with "other worlds. Other worlds are interfaces,
where object orientation is not supported or is not the best decision.... read more

Posted by Mario Linke 2007-03-04

SOJO release version 0.3.0

The Open Source project Sojo has announced the third release (version 0.3.0).
The intention for this project is a Java framework, that convert JavaBeans in a simplified representation .
So it is easy and uniformly to handle and control the access to JavaBeans properties.
This framework want to complement POJOs, where Java communicate with "other worlds. Other worlds are interfaces,
where object orientation is not supported or is not the best decision.... read more

Posted by Mario Linke 2007-01-08

second SOJO release version 0.2.0

The Open Source project Sojo has announced the second release (version 0.2.0).
The intention for this project is a Java framework, that convert JavaBeans in a simplified representation .
So it is easy and uniformly to handle and control the access to JavaBeans properties.
This framework want to complement POJOs, where Java communicate with "other worlds. Other worlds are interfaces,
where object orientation is not supported or is not the best decision.... read more

Posted by Mario Linke 2006-11-06

Initial release from sojo version 0.1.0

Are Plain Old Java Objects (POJOs) to complex?

POJOs are very importend for the development. With POJOs you can develop object orientated and independent from often changed technologies.

But what is with cases, where Java must communicate with "other worlds". Other worlds are interfaces,
where object orientation is not supported or is the best decision. For example by:

* operation of complex Java-Objects-graphs:
- copy or clone complex object graph (can manage different version (object history) from one object graph)
- compare complex object graph
- extend objects to additional information (e.g.: object-versions (number of changes), change date or user)
- easy navigate on the complex object graph
- serialize complex object graph without implementation from the interface java.io.Serializable
- making object-values immutable, for testing concurrent access - multi threading)
* remote acces/communication:
- HTTP protocol - request and response are based on String represantation
- RMI (Java-Object must serializable (marshalling) or deserializable (unmarshalling))
- WebService or XML RPC - convert Java-Object in special String represantation, in XML
- create value object/transfer object to transport over the network
* data access:
- object/relational persistence respectively object/relational mapping
- flat files (convert Java-Object-Graph to a flat represantation)
- property files (e.g. convert Strings to Long, Date, ... by reading a property file and map the value to setter from a Bean)
- legacy systems
* GUI interface:
- transform business models to GUI-models (DataBinder)
- every changes on the GUI-model must to notice (integrated PropertyChangeListener or VetoableChangeListener)
* and so on ... ... read more

Posted by Mario Linke 2006-10-15