On Sun, 7 Jul 2002 19:30, Stephen McConnell wrote:
> Would have liked to have seen more collaboration on the defintion - but
> its not problem - excalibur.meta is in place which is critical for any
> real container development (actually what I should say is that
> seperation of meta data is critical). I'm getting to the point where I
> have a reasonbably good idea of the seperation that's needed:
>
> * kernel - the thing runs a container
> * container - a thing that manages meta data (kernel specific)
> * type loader - a thing that handles internalization of meta info
> from XML or serialized form to a meta info implementation
> (can be generalized across kernels/containers)
> * profile loader - a thing that handles internalization of profiles
> (container specific)
>
> So at the end of the day, what's needed is stability on:
>
> (a) a meta-info factory that takes a loader implementation class
> and a source (configuration or serialized form) and returns an
> object instance that is the meta-info representing the type.
> (b) a really stable DTD for the .xinfo document
>
> Both of the above should established be in a seperate package (possibly
> as part of framework 4.2). Seperation of the above two would ensure
> minimal pain as this area evolves - and there will be pain because
> little things (like package names in DTD that reference containerkit)
> will propergate across lots of components. Instead - seperate out the
> very first interoperability layer (the internalization from XML) - get
> in place very good documentation and a test suite and we will have
> something tangible to work with.
>
> Pete - do you think that's reasonable?
I dont see any advantage for me in doing it that. Theres no chance of you ever
doing some of the things you want to do in anything I am involved with. You
dont seem to want to do it the way I have suggested, hence you will only end
up whining again. I think the best idea would be for you to do with merlin
whatever you want and be done with it.
The metainfo layer is already incompatible and this incompatability is only
going to incerase in the future. Given your designs I suspect that merlin
enhanced metainfo files will not load in any other containers anyhow.
So what possible reason could I have to work with you? Merlin does not have
any components I need or want and unlikely to have any in the future. I am
done arguing and thus it is less work to route around you than to try and
work with you. I have achieved a model that will enable compatability of
components between Myrmidon, Cocoon and Phoenix which is what I set out to
achieve. The only draw card was that I would not have to write the stuff that
is likely to be in Merlin. However thats not likely to occur, so I will have
to rewrite it all anyway.
If you want to use what I write, feel free to. If you want to extend the stuff
in ways that I suggested then I will help you. If you want to do your own
stuff then feel free. I wont let you push it into framework as it is not
going to be what Phoenix, Myrmidon (or Cocoon hopefully) uses.
--
Cheers,
Peter Donald
'Most men would rather die than think. Many do.'
Bertrand Russell
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
