directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <>
Subject Turning Service Impls into POJOs
Date Sun, 07 Dec 2003 19:10:17 GMT


Take a look here:


Service Interface




Here's another service:


Service Interface




BTW Subversion ROCKS!!! - couldn't help but say that!!!


As you can see I have begun to write POJOs instead of services and wrap them

into container specific adapters.  This way all of Eve's component's for
both the

frontend and the backend will be compatible with any container supplying an

adapter.  Take a look at the Merlin (prefix) based adapters that I have
written in the respective

implementation directories.  


The POJOification process has the following benefits:


*	components can be tested without having to bend over backwards while

       dealing with containers.

*	POJO's are easier for people on the team to understand and work with

do not need to be experts in the container world.

*	the work that needs to be done on a per-container basis can be done

       those that actually have the proficiency with a specific container.

*	the monitor concept is a good idea that is more useful than plain
old logging.

It allows us to decouple the component from the container where logging is

concerned.  The monitor interface provided by the POJO service clearly

              what is worth monitoring or logging if that's what the monitor
is to do.  For

              more info on this topic take a look at the following Wiki




              Take a look at the monitor interfaces in the SPI directories
for each of these

              services while reading the wiki page.  This page was
originally written by

              Leo Sutic.


Just to clarify this is not an attempt to make things work with Pico.  It's
what's right to

do to make the components/services easier to manage, more testable with mock

and compatible with any container/kernel that comes out of Avalon or
anywhere else.


The bottom line is to remain container independent while enabling the

use of any container at the same time.  The POJOification process does this



I personally plan to support Avalon's Merlin however this opens the door for

use of these services in any other containers.  If people are willing to
support other

containers by contributing adapters we'll take patches and add em to our






View raw message