embedlets-developer

[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

RE: [Embedlets-dev] [Arch] Properties and such

[James C. <ca...@vi...>]

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

+1

JC


> -----Original Message-----
> From: emb...@li...
> [mailto:emb...@li...]On Behalf Of
> Andrzej Jan Taramina
> Sent: Tuesday, February 11, 2003 10:52 AM
> To: emb...@li...
> Subject: [Embedlets-dev] [Arch] Properties and such
>
>
> Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
> _______________________________________________
>
> 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
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>
>

[Embedlets-dev] Re: [Arch] Properties and such

[Ted K. <tk...@ya...>]

Andrzej,

>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?



Yes.  And I very much appreciate the extra time you have taken in your recent
emails to lay all of these ideas out in meticulous detail.  I have not been
exposed to a number of these ideas before and it is taking me some time for me
to digest them.

I think that I am finally starting to see where you are going with the
Architecture and I must say is it blowing my mind.  Your explanation of how
Servlets really were components was what punctured the paradigm bubble I had
been working under.   After re-studying the ideas you have laid out in your
recent posts (like the various advantages of using context objects over
instance variables) I am starting to see that you have been working at a whole
abstraction level higher than I have been.

I know that the posts that explained these ideas had to have been a PITA to
develop but perhaps you will be consoled by the fact that they are going to
provide an excellent base for the site documentation that we will need to
develop in order to explain this stuff to the rest of the world.

I must say that whatever effort I have put into helping out with this project
so far has already paid for itself many times over with just the new knowledge
I have gained. :-)


Ted

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com