At 08:57 AM 6/27/2002 +0200, you wrote:
> > With enough annotations you could almost validate the entire sitemap prior
> > to deploying it which would probably save a lot of headaches over time.
>
>is the current metainfo material you guys are writing startup-only? It
>has been said cocoon's sitemap changes at runtime
And I would put it to you that it doesn't. The other Leo has said much the
same thing.
> Component Entrys
> > ----------------
> >
> > When a container is managing a component it creates an Entry per
> component.
> > The Entry manages all the runtime information associated with a component.
>
>not the Assembly Profile?
maybe a reference to Profile
> > The handlers is one of the main places where the containers will differ.
> > Some will offer pooling and advanced resource management. Others will
> proxy
> > access to components, maybe offering interceptors etc.
>
>what is the minimum? ie what should the-other-leos MicroContainer
>support?
See SimpleServiceKernel for an example of basic container. Does little bar
run things.
> The Component/Application Profile classes provide a basis for all the
> > Profile information. However it is possible that some containers will
> > extend these classes to provide specific information relevent only to the
> > particular container. However for many containers (ie Phoenix and
> Fortress)
> > the base Profile classes should be sufficient.
>
>do we make it a specification of the standard Profile classes that they
>are sufficient for Phoenix/Fortress (or do we specify phoenix/fortress
>don't support more than the standard Profile). I'd like that.
It is just how they happen to stand at this stage of evolution.
Fortres//Phoenix are free to extend them in future if needed.
>seems to me the basic definition of Entry
>
>public interface Entry
>{
> ComponentMetaData getMetaData();
> RuntimeContext getRuntimeContext();
> Handler getHandler();
>}
>
>or something similar could be common to many containers (ie
>Handler/ComponentEntry stuff can partially be in containerkit)
Similar in concept but implementations vary. Making all container implement
a heavy weight interface like the above would never fly.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
