[Embedlets-dev] [Arch] Properties and such

[Andrzej J. T. <an...@ch...>]

Chris suggests:

> 1. The Properties service reads the input media (eg. XML) and encounters an
> object.
> 2. The Properties service instantiates the object based on the 'class'
> attribute on the stream. The objects' Class is assumed to be preloaded in
> the installation, thus avoiding byte code streaming.
> 3. The object implements the PropertyAccess interface (orginally called
> Persistent), which defines the readProperties(Properties p) method.
> 4. The component reads its properties using getProperty(String Name) methods
> of the Properties object. Components can access other objects by reference
> using getObjectProperty(objectName).
> 5. The container manages the life cycle processes by informing each
> component of its current state: create (implied in constructor), initialize,
> start, stop, terminate.

Yup....I agree.  And it's even easier if the objects being reconstituted are 
Context objects, rather than an Embedlet itself, separating the data-oriented 
from the process-oriented in a clean way.

I think this approach is a good one.  It allows serialization where it makes 
sense (regardless of encoding technique: binary, XML, code generated, 
something else), can be used to create a generic Persistence service (in the 
long term sense).

I think we've finally put this one to bed to everyone's satisfaction.  Agreed?


Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com